Hi,
we get the same exception trace using Maven 2.2.1 and after upgrading
to javadoc plugin 2.6. Now we use the aggregate goal in a report set
instead of the aggregate config parameter.
We hava a mulit-module build with two layers of aggregation:
A-parent
- A1
- A2
- B-parent
- B1
,
Holger
Holger Brands wrote:
Hi,
we get the same exception trace using Maven 2.2.1 and after upgrading
to javadoc plugin 2.6. Now we use the aggregate goal in a report set
instead of the aggregate config parameter.
We hava a mulit-module build with two layers of aggregation:
A-parent
I've a multi-module build that is compiled with target 1.6 and deployed to
our company repo with artifactIds artifact1, artifact2 and so on.
Now, what I want to achieve is the following:
I want the same multi-module build optionally to be compiled with target 1.5
and deployed to our company repo
and unpacks it's -source.jar and does a recompile with the different jdk
On 25 September 2008 12:00, Holger Brands [EMAIL PROTECTED] wrote:
I've a multi-module build that is compiled with target 1.6 and deployed
to
our company repo with artifactIds artifact1, artifact2 and so on.
Now, what I
.
Perhaps what you want is a different project that depends on the first one
and unpacks it's -source.jar and does a recompile with the different jdk
On 25 September 2008 12:00, Holger Brands [EMAIL PROTECTED] wrote:
I've a multi-module build that is compiled with target 1.6 and deployed
and is not expanded to artifactId1_java.
That's the only thing that's missing.
Any ideas?
Thanks,
Holger
Holger Brands wrote:
Hi Nick,
I (already) tried to use a profile in the parent pom, but the adapted
finalName is ignored by the jar plugin, e.g. mvn package creates the jar
to extract
foo-jdk15-sources-${project.version}.jar into target/generated-sources/jar
and use the build helper plugin to add this source path...
That should do what you need and allow you to differentiate the
depenencies
required for each platform (jdk15 vs jdk16)
2008/9/25 Holger Brands [EMAIL
Hi,
I noticed, that the codehaus snapshot repo
(http://snapshots.maven.codehaus.org/maven2)
is available again.
But unfortunately, it is not up to date, e.g. deployments from May, 11th are
missing
(for example new versions of webstart and keytool plugin).
Can somebody comment on the state of
Hi,
You should check Bob McWhirter's Blog on http://www.fnokd.com/ for
status updates on the Codehaus server recovery. Additional information
can be found on the temporary Codehaus frontpage http://www.codehaus.org/
Thanks for these links.
But I have not found any info regarding the
