Now Beta2 Build 201102111519 is asking for installing junit at the first run. But if the user choose to not install it, junit libraries are still being added to java projects by default. They should be not added to the project as the user decided not to use junit.

I don't know if including org.netbeans.libs.junit4 module will solve this or I should open a new issue.

(In reply to comment #1)
> Now Beta2 Build 201102111519 is asking for installing junit at the first run.

That is unrelated to this issue, which is about Maven repository generation; please do not discuss here.

> junit libraries are still being added to java projects by default

In Beta 2 yes; not in development builds.

Any ideas or tips how the org.netbeans.libs.junit4 module could incorporated into maven repo generation?

(In reply to comment #3)
> tips how the org.netbeans.libs.junit4 module could incorporated
> into maven repo generation?

Well, you pass a netbeansInstallDirectory to the mojo; libs.junit4 needs to be there somewhere. It is built in the extra cluster during a regular source build, or you can use the <autoupdate> task to install org-netbeans-libs-junit4.nbm.

The issue seems to be fixed for the trunk and the release70 branch. The one branch is still missing, the release70_beta2 branch. The org-netbeans-libs-junit4.nbm is not part of the stable.uc cluster thus it's not part of the unpacked-nbms job result.

Is that correct configuration or the org-netbeans-libs-junit4.nbm is missing from the stable.uc cluster configuration?

org.netbeans.libs.junit4 was built as a regular part of the platform cluster in Beta 2.

However the definition of nb.cluster.platform doesn't contain any junit definition in the cluster.properties file besides the string "libs.junit4" isn't presented in the cluster.properties file at all.

(In reply to comment #7)
> the definition of nb.cluster.platform doesn't contain any junit
> definition in the cluster.properties file

Just in Beta 2, I think, since that used a now-abandoned method for distributing JUnit to users. libs.junit4 can still be built directly in this branch, and it should be published on the Maven repo (with an appropriate external link to junit:junit:4.8.2).

The issue is fixed and the maven repository with 70-beta2 artifacts has been released.

Not really a 70_HR_FIX since there was no source code change to backport - just a change in RE process.

understood - so removing keyword ;)

Looks to be working. http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-libs-junit4/RELEASE70/ exists. *.pom refers to junit:junit:4.8.2 as expected. *.nbm contains just netbeans/modules/ext/junit-4.8.2.jar.external as expected. *.jar manifest specifies Maven-Class-Path: junit:junit:4.8.2 as expected.

http://bits.netbeans.org/netbeans/trunk/maven-snapshot/org/netbeans/api/org-netbeans-libs-junit4/SNAPSHOT/ also looks OK.

I hope that the special treatment of this module was included in the repository publishing script so it will apply also to future releases, not just done as a one-off manual step.

> I hope that the special treatment of this module was included in the repository
> publishing script so it will apply also to future releases, not just done as a
> one-off manual step.

The special treatment isn't a manual step however it isn't part of any repository script so far. It's only the script in the Hudson infrastructure. I plan to create a script for maven repo generation and include it into the mercurial repository.

By "repository publishing script" I meant "script to publish a [Maven] repository", not "publishing script in the [Mercurial] repository". But it would indeed be useful to have this script kept somewhere in nbbuild.