Re: Maven Exec - Inheritance - Multi Module Build

[Karl Heinz Marbaise]

Hi Anders,
what you mentioned is correct, but this does not solve my problem...

BTW: The usage works for MVN 2.2.1 and MVN 3.0 - Alpha 5...but i've checked
the docs and you're right...


Anders Hammar wrote:
> 
> I just wanted to mention that defining two plugin sections of the same
> plugin (exec-maven-plugin in your case) is incorrect. I believe there is a
> bug in som Maven versions that allow that, but it's not te corredt way of
> doing things. Instead, you should specify two execution sections in the
> same
> plugin section.
> 
> 

Kind regards
Karl Heinz Marbaise
-- 
View this message in context: 
http://old.nabble.com/Maven-Exec---Inheritance---Multi-Module-Build-tp26779913p26790912.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Enabling fileset packaging with archetype-metadata.xml

[nklein]

I trying to set up my Maven archetype so the directory layout for
ActionScript files can be updated through the package setting. This provides
ActionScript with the same functionality available to Java files.

I've read
http://maven.apache.org/plugins/maven-archetype-plugin/advanced-usage.html
and performed a
$ mvn archetype:create-from-project
-Darchetype.properties=../archetype.properties

where the archetype.properties file contains:

archetype.filteredExtensions=as
archetype.languages=ActionScript

When this command is executed, then the archetype-metadata.xml file is
updated so that filtering is enabled for *.as files:

   // packaged defaults to false
src/test/flex
 
 **/*.as
 
 

But to get the package setting to be recognized, then the packaged option
also needs to be enabled for this fileset. 

It doesn't seem like I can just update this file to turn on
packaging="true", because then Maven seems to become confused and doesn't
perform directory layout correctly (it prepends the new package name but
doesn't remove the old one in some places but not all); it also isn't a good
idea to be directly modifying Maven's internal XML files. This type of
modification should only be performed through Maven commands.

I have looked through archetype:create-from-project's optional parameters
but haven't found any optional parameter that turns on the packaged
attribute for a particular language (analogous to
archetype.filteredExtensions) that can be added to the properties file. 

Thanks, Norman



-- 
View this message in context: 
http://old.nabble.com/Enabling-fileset-packaging-with-archetype-metadata.xml-tp26783357p26783357.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: To use version for maven.plugins or not to use, that is the question :)

[Barrie Treloar]

On Tue, Dec 15, 2009 at 7:09 AM, Qureshi,Shahzad [Ontario]
 wrote:
> Hi all,
>
> I wanna know the standard and the reasons behind it.
>
> I want to find out if I should specify a version for a maven plugins, lets 
> say maven-javadoc-plugin, or not to specify it and in which case the default 
> one will be used. At this point, I don't specify versions
>
> I recently setup Nexus at my work and started seeing all these errors where 
> Nexus wouldn't find snapshot version for plugins, maven-javadoc-plugin being 
> one of them. The maven-javadoc-plugin is at 2.6.2-SNAPSHOT right now, but my 
> settings.xml is not setup to take care of this scenario.

In general, you NEVER want to work with snapshots.
You would only use a snapshot of a plugin if you wanted to test that a
critical bug has been fixed and then you would request that the plugin
get officially released (and if you can't wait for that, build an
internal release).

If you start including snapshots in your build process your build can
suddenly break and your build is not reproducible (since SNAPSHOTS by
definition change over time)

That said, as others have pointed out, the best pracitce is to create
an organizational parent pom and declare versions there and have your
project poms use this parent pom.
That way you have control over when to upgrade.

If you are lazy (we are) then you can leave off the version and use
whatever the latest released version gets pulled down and only if the
build breaks to set the version to one that works.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Doxia Tools 1.2 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Doxia
Tools, version 1.2

This shared component has some utilities that are useful when
integrating Doxia in Maven, mainly for site generation and report
creation. The main entry point is the SiteTool Plexus component.

http://maven.apache.org/shared/maven-doxia-tools/


Release Notes - Maven Shared Components - Version maven-doxia-tools 1.2

** Improvement
* [MSHARED-137] - initialize lastModified value of DecorationModel
with site.xml file lastModified value


** Task
* [MSHARED-138] - Update to doxia 1.1.2


Enjoy,

-The Maven team



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: To use version for maven.plugins or not to use, that is the question :)

[Anders Hammar]

And Maven 3 will also complain (well, inform) about this.

/Anders

On Mon, Dec 14, 2009 at 22:09, Justin Edelson wrote:

> Yes - use a version.
>
> Set up an organizational pom and use it as the parent for all of your
> projects. Use the pluginManagement section of the organizational pom to
> declare plugin versions.
>
> Unless you do this, your builds aren't fully reproduceable.
>
> Justin
>
> On Mon, Dec 14, 2009 at 3:39 PM, Qureshi,Shahzad [Ontario] <
> shahzad.qure...@ec.gc.ca> wrote:
>
> > Hi all,
> >
> > I wanna know the standard and the reasons behind it.
> >
> > I want to find out if I should specify a version for a maven plugins,
> lets
> > say maven-javadoc-plugin, or not to specify it and in which case the
> default
> > one will be used. At this point, I don't specify versions
> >
> > I recently setup Nexus at my work and started seeing all these errors
> where
> > Nexus wouldn't find snapshot version for plugins, maven-javadoc-plugin
> being
> > one of them. The maven-javadoc-plugin is at 2.6.2-SNAPSHOT right now, but
> my
> > settings.xml is not setup to take care of this scenario.
> >
> > It seems that I've to do what example 14.2 at this link:
> >
> http://svn.sonatype.org/m2eclipse/trunk/org.maven.ide.eclipse.book/book/ch14s03.htmlsays
> >
> > And in which case I've to use -Ppublic-snapshots flag during my
> packaging.
> >
> > Now what is the general standard in a case like this? I can easily do
> what
> > the link above suggests or just specify a version. I've reservations with
> > both of them and see advantages for both of them as well.
> >
> > What do the gurus suggest? :)
> >
> > Thanks
> >
> >
> >
> > 
> > Shahzad Qureshi
> > Systems Analyst/Programmer
> > Applications Directorate | La direction générale des applications
> > Chief Information Officer Branch | Direction générale du dirigeant
> > principal de l'information
> > Environment Canada | Environnement Canada
> > shahzad.qure...@ec.gc.ca
> > Telephone | Téléphone 416-739-4702
> > Government of Canada | Gouvernement du Canada
> > Website | Site Web www.ec.gc.ca
> >
> >
>

[ANN] Sonar 1.12 Released

[Freddy Mallet]

The Sonar Team is pleased to announce the 8th and last major Sonar release
of the year.

Around 60 improvements and bug fixes are contained in this new version and
the main features are :

*  Ability to manage authentication and authorization by project
*  Ability to ignore violations with the new ‘//NOSONAR’ comment. This is a
very simple and generic way to eliminate false positive generated for
instance by Findbugs or any kind of rules engine.
*  Highlighted code syntax, because code is not just a bunch of plain black
text

To get more information : http://sonar.codehaus.org/downloads/
To see Sonar in action : http://nemo.sonarsource.org

Enjoy,

- The Sonar team


Freddy Mallet
www.SonarSource.com
Sonar.codehaus.org
http://twitter.com/FreddyMallet

Re: To use version for maven.plugins or not to use, that is the question :)

[Justin Edelson]

Yes - use a version.

Set up an organizational pom and use it as the parent for all of your
projects. Use the pluginManagement section of the organizational pom to
declare plugin versions.

Unless you do this, your builds aren't fully reproduceable.

Justin

On Mon, Dec 14, 2009 at 3:39 PM, Qureshi,Shahzad [Ontario] <
shahzad.qure...@ec.gc.ca> wrote:

> Hi all,
>
> I wanna know the standard and the reasons behind it.
>
> I want to find out if I should specify a version for a maven plugins, lets
> say maven-javadoc-plugin, or not to specify it and in which case the default
> one will be used. At this point, I don't specify versions
>
> I recently setup Nexus at my work and started seeing all these errors where
> Nexus wouldn't find snapshot version for plugins, maven-javadoc-plugin being
> one of them. The maven-javadoc-plugin is at 2.6.2-SNAPSHOT right now, but my
> settings.xml is not setup to take care of this scenario.
>
> It seems that I've to do what example 14.2 at this link:
> http://svn.sonatype.org/m2eclipse/trunk/org.maven.ide.eclipse.book/book/ch14s03.htmlsays
>
> And in which case I've to use -Ppublic-snapshots flag during my packaging.
>
> Now what is the general standard in a case like this? I can easily do what
> the link above suggests or just specify a version. I've reservations with
> both of them and see advantages for both of them as well.
>
> What do the gurus suggest? :)
>
> Thanks
>
>
>
> 
> Shahzad Qureshi
> Systems Analyst/Programmer
> Applications Directorate | La direction générale des applications
> Chief Information Officer Branch | Direction générale du dirigeant
> principal de l'information
> Environment Canada | Environnement Canada
> shahzad.qure...@ec.gc.ca
> Telephone | Téléphone 416-739-4702
> Government of Canada | Gouvernement du Canada
> Website | Site Web www.ec.gc.ca
>
>

Re: Maven PDF Plugin Problems

[Lukas Theussl]

The pdf plugin doesn't support multi-module projects (yet):
http://jira.codehaus.org/browse/MPDF-8

HTH,
-Lukas



On Mon, Dec 14, 2009 at 6:20 PM, Neil Chaudhuri <
nchaudh...@potomacfusion.com> wrote:

> I am attempting to use the latest Maven PDF plugin just published with
> my multi-module Maven project. Even though site generation is working
> for me, I am having some issues with the PDF plugin and have a few
> questions:
>
>
>
> 1)  Why must I have a "site" directory in every module?
>
> 2)  When I add a "site" directory to every module at the "src"
> level, I get a PDF generated, but it just has a title page and footers
> but no actual content. What am I missing here?
>
>
>
> Thanks.
>
>

Re: maven assembly plugin - the artefact size is multiplied by 2

[le squere, vincent]

I've tried to use winzip, 7-zip, and to extract with the jar command.
It's always the same message, this archive is not a valid archive.

So I can't see its contents.

Just a precision, my assembly work fine on windows, the problem is just on 
debian.
The JDK I use is  1.6.0_16-b01


>But, when the size of my ear is more than 20Mo, the size is multiplied by
> 2 in the destination folder.
>I thought that it just makes a copy.

Use Winzip or similar to unpack the Ear and look at the contents. You
can probably figure out what's going on with a little more
information, but just saying "its twice the size" without knowing
anything more about it makes it tough to say why its happening.

Wayne
This 
message contains information that may be privileged or confidential and is the 
property of the Capgemini Group. It is intended only for the person to whom it 
is addressed. If you are not the intended recipient, you are not authorized to 
read, print, retain, copy, disseminate, distribute, or use this message or any 
part thereof. If you receive this message in error, please notify the sender 
immediately and delete all copies of this message.

To use version for maven.plugins or not to use, that is the question :)

[Qureshi,Shahzad [Ontario]]

Hi all,

I wanna know the standard and the reasons behind it.

I want to find out if I should specify a version for a maven plugins, lets say 
maven-javadoc-plugin, or not to specify it and in which case the default one 
will be used. At this point, I don't specify versions

I recently setup Nexus at my work and started seeing all these errors where 
Nexus wouldn't find snapshot version for plugins, maven-javadoc-plugin being 
one of them. The maven-javadoc-plugin is at 2.6.2-SNAPSHOT right now, but my 
settings.xml is not setup to take care of this scenario.

It seems that I've to do what example 14.2 at this link: 
http://svn.sonatype.org/m2eclipse/trunk/org.maven.ide.eclipse.book/book/ch14s03.html
 says

And in which case I've to use -Ppublic-snapshots flag during my packaging. 

Now what is the general standard in a case like this? I can easily do what the 
link above suggests or just specify a version. I've reservations with both of 
them and see advantages for both of them as well.

What do the gurus suggest? :)

Thanks 




Shahzad Qureshi
Systems Analyst/Programmer
Applications Directorate | La direction générale des applications
Chief Information Officer Branch | Direction générale du dirigeant principal de 
l'information
Environment Canada | Environnement Canada
shahzad.qure...@ec.gc.ca
Telephone | Téléphone 416-739-4702
Government of Canada | Gouvernement du Canada
Website | Site Web www.ec.gc.ca

Re: filteredExtensions doesn't work

[nklein]

By default, Maven only recognizes a limited set of languages. When a
language is recognized then Maven performs filtering on files ending in the
language suffix (such as *.java). This example demonstrates the filtering
difference between Java (recognized) and ActionScript (unrecognized) files:

[DEBUG] Processing fileset src/main/java (Filtered-Packaged) [**/*.java -- ]

[DEBUG] Copying fileset src/main/flex (Copied-Flat) [**/*.jpg, **/*.db,
**/*.TTF, **/*.png, **/*.flv, **/*.otf, **/*.mxml, **/*.as, **/*.swf,
**/*.css -- ]

According to
http://maven.apache.org/plugins/maven-archetype-plugin/examples/create-with-property-file.html,
there are two arguments (archetypeLanguage and archetypeFilteredExtensions)
that need to be set to enable the recognization of a language. Although they
describe specifying these arguments within a properties file, it also states
that these arguments can also be specified on the command line like this:

$ mvn -X archetype:generate -DarchetypeCatalog=local 
 -DarchetypeLanguage=actionscript 
 -DarchetypeFilteredExtensions=as

Unfortunately this still results in *.as files only being copied and not
processed.

I have also tried all of the different permutations, such as creating and
specifying the values within a project file, but still haven't managed to
get ActionScript as files to be filtered by Maven.

Thanks, Norman 


-- 
View this message in context: 
http://old.nabble.com/filteredExtensions-doesn%27t-work-tp26779943p26779981.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Exec - Inheritance - Multi Module Build

[Anders Hammar]

I just wanted to mention that defining two plugin sections of the same
plugin (exec-maven-plugin in your case) is incorrect. I believe there is a
bug in som Maven versions that allow that, but it's not te corredt way of
doing things. Instead, you should specify two execution sections in the same
plugin section.

/Anders

On Mon, Dec 14, 2009 at 17:36, jabba  wrote:

>
> Hi,
>
> i'm testing a setup with Maven and a combination of Java/Non Java Projects
> (using RPM plugin etc.)...
>
> I'm using a parent to bind some calls to exec plugin to particular phases:
>
> 
>   
>  
>   org.codehaus.mojo
>exec-maven-plugin
>1.1.1
>
>
>initialize
>initialize
>
>exec
>
>
>cmake
>
>
>.
>
>
>
>
>
>
>
>org.codehaus.mojo
>exec-maven-plugin
>1.1.1
>
>
>compile
>compile
>
>exec
>
>
>make
>
>
>
>
>   
> 
> ...
> Using the rpm-plugin in modules is working like a charm...so far so
> good
>
> but now i reached a little problem, cause i have a piling project which
> does
> not need any calls to the above exec parts...but based on my configuration
> they are of course called as defined
>
> Is there a way to prevent calling the exec's in a sub-module which inherits
> the parent pom information
>
> Kind regards
> Karl Heinz Marbaise
> --
> View this message in context:
> http://old.nabble.com/Maven-Exec---Inheritance---Multi-Module-Build-tp26779913p26779913.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: AW: pom.xml : element

[Mirko Friedenhagen]

Am 14.12.2009 um 13:08 schrieb Mark Struberg:
> the  element in the pom is used for every SCM action in maven, e.g. if 
> you do a mvn release:prepare / mvn release:perform and stuff.
> 
> Since Hudson and other CI environments often do not rely on the build system 
> for updating the project, they have the ability to do this their self (otoh, 
> some CI systems do use maven-scm internally, but get the scm URL parameter 
> from the UI rather than the pom.

Hm, just lately I tried the following with a project in Subversion:
- Checked out a project from trunk


scm:svn:file:///Software/nobackup/svn/myproject/branches/stable

scm:svn:file:///Software/nobackup/svn/myproject/branches/stable




maven-release-plugin


file:///Software/nobackup/svn/myproject/releases



- Both developerConnection and connection in the pom point to branches/stable
- My goal was to have releases built from this stable branch and tags landing 
under releases.
- When I issued "mvn release:prepare" from the trunk checkout not the 
branches/stable version was released but the (trunk) working copy was copied to 
releases.

Best Regards
Mirko
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Memory Issues with site and javadoc reports.

[Ryan Connolly]

Update... I've solved this in my build by using the 2.3 version of
maven-javadoc-plugin instead of the 2.6.1.  I'll test other versions between
2.3 and 2.6.1 as time permits.

Thanks,
-Ryan

On Mon, Dec 14, 2009 at 1:11 PM, Ryan Connolly  wrote:

> Hello, I'm hoping someone may be able to assist me with a Maven Site
> generation issue I've been having ever since I added a fourth module to my
> multi-module build.  The issue appears to be linked to the
> maven-javadoc-plugin and I'm hoping someone here may have some insight into
> how I may be able to fix this problem.
>
> I am running mvn site with MAVEN_OPTS=-Xmx512m as the site goal runs out of
> memory without this set.  However, this appears to conflict with the javadoc
> reports as I am gettting the following stack trace:
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
> generation
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>  at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>  at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
>  at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>  at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>  at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>  at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
>  at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error during
> page generation
>  at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
>  at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>  at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>  ... 22 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
> rendering Maven report: Error occurred during initialization of VM, try to
> reduce the Java heap size for the MAVEN_OPTS environnement variable using
> -Xms: and -Xmx:.
>  at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
>  at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
>  at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
>  at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
>  at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
>  ... 24 more
> Caused by: org.apache.maven.reporting.MavenReportException: Error occurred
> during initialization of VM, try to reduce the Java heap size for the
> MAVEN_OPTS environnement variable using -Xms: and -Xmx:.
>  at
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getModulesLinks(AbstractJavadocMojo.java:4706)
>  at
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addLinkofflineArguments(AbstractJavadocMojo.java:3226)
>  at
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addStandardDocletOptions(AbstractJavadocMojo.java:4041)
>  at
> org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1803)
>  at
> org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:124)
>  at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
>  ... 28 more
> Caused by: org.apache.maven.shared.invoker.MavenInvocationException: Error
> occurred during initialization of VM, try to reduce the Java heap size for
> the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.
>  at
> or

Getting Flex to respond like Java to the package argument

[nklein]

Files that end with a java suffix respond to the package argument by 

[DEBUG] Processing fileset src/main/java (Filtered-Packaged) [**/*.java -- ]

This results in their directory layout being updated to reflect the value of
the package argument.

It appears that all other file suffixes are either Filtered-flat or
Copied-Flat:

I was hoping that setting  to src/main/flex would be
enough, but apparently Maven still doesn't know how to handle Flex
ActionScript files since its just copying them

[DEBUG] Copying fileset src/main/flex (Copied-Flat) [**/*.jpg, **/*.db,
**/*.TTF, **/*.png, **/*.flv, **/*.otf, **/*.mxml, **/*.as, **/*.swf,
**/*.css -- ]

How can I signal to Maven that it should handle Flex ActionScript "as" files
in the same manner as Java files, so they are Filtered-Packaged.

I'm hoping there is a single option and that I won't need to explicitly
update the directory layout using filesets as this would be a more elegant
solution.

thanks, Norman
-- 
View this message in context: 
http://old.nabble.com/Getting-Flex-to-respond-like-Java-to-the-package-argument-tp26779943p26779943.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Memory Issues with site and javadoc reports.

[Ryan Connolly]

Hello, I'm hoping someone may be able to assist me with a Maven Site
generation issue I've been having ever since I added a fourth module to my
multi-module build.  The issue appears to be linked to the
maven-javadoc-plugin and I'm hoping someone here may have some insight into
how I may be able to fix this problem.

I am running mvn site with MAVEN_OPTS=-Xmx512m as the site goal runs out of
memory without this set.  However, this appears to conflict with the javadoc
reports as I am gettting the following stack trace:
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error during page
generation
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
 at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:105)
 at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
 at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
 ... 22 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: Error occurred during initialization of VM, try to
reduce the Java heap size for the MAVEN_OPTS environnement variable using
-Xms: and -Xmx:.
 at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:149)
 at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
 at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
 at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
 ... 24 more
Caused by: org.apache.maven.reporting.MavenReportException: Error occurred
during initialization of VM, try to reduce the Java heap size for the
MAVEN_OPTS environnement variable using -Xms: and -Xmx:.
 at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getModulesLinks(AbstractJavadocMojo.java:4706)
 at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addLinkofflineArguments(AbstractJavadocMojo.java:3226)
 at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addStandardDocletOptions(AbstractJavadocMojo.java:4041)
 at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1803)
 at
org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:124)
 at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
 ... 28 more
Caused by: org.apache.maven.shared.invoker.MavenInvocationException: Error
occurred during initialization of VM, try to reduce the Java heap size for
the MAVEN_OPTS environnement variable using -Xms: and -Xmx:.
 at
org.apache.maven.plugin.javadoc.JavadocUtil.invokeMaven(JavadocUtil.java:1081)
 at
org.apache.maven.plugin.javadoc.AbstractJavadocMojo.getModulesLinks(AbstractJavadocMojo.java:4689)
 ... 33 more

The javadoc plugin version being used is 2.6.1.

Please let me know if I have not included enough information here for folks
to help me get around this issue and I will provide whatever is needed.

Thank you!
-Ryan

Re: maven assembly plugin - the artefact size is multiplied by 2

[Wayne Fay]

>    But, when the size of my ear is more than 20Mo, the size is multiplied by 
> 2 in the destination folder.
>    I thought that it just makes a copy.

Use Winzip or similar to unpack the Ear and look at the contents. You
can probably figure out what's going on with a little more
information, but just saying "its twice the size" without knowing
anything more about it makes it tough to say why its happening.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Doxia macro for links to xref sources

[Johannes Schneider]

Hi,

does anybody out there has any experience how linking to the xref
sources should be done?
I'd like to just add the FQN for my class and let doxia do the rest...
Any ideas?


Johannes

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Info report license LGPL

[Martin Scholl]

Isn't there anyone who ran in the same issue before or, at least, has  
a hint where to dig?



Am 10.12.2009 um 14:56 schrieb Martin Scholl:


Hi,

I have a maven project, where I specified "LGPL" as license. If the  
project site is generated (or the license goal is explicitly  
invoked) the resulting license.html says, that the "Project License"  
is "GNU Lesser Public License", but all links and texts below (about  
the license) are about GPL and not LGPL. Is this a known bug or did  
I do something wrong?


Thanks in advance.

Cheers.

Martin

PS: Here is the link to the "wrong" project license site: 
http://www.enviromatics.net/charon/license.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Maven PDF Plugin Problems

[Neil Chaudhuri]

I am attempting to use the latest Maven PDF plugin just published with
my multi-module Maven project. Even though site generation is working
for me, I am having some issues with the PDF plugin and have a few
questions:

 

1)  Why must I have a "site" directory in every module?

2)  When I add a "site" directory to every module at the "src"
level, I get a PDF generated, but it just has a title page and footers
but no actual content. What am I missing here?

 

Thanks.

maven assembly plugin - the artefact size is multiplied by 2

[le squere, vincent]

Hello,
I'm working on a multi-module project.
This project contains an ear artifact, which is correctly generated.

I'm also using maven-assembly-plugin (tried with version 2.2-beta-2 to 
2.2-beta-4), to group all the artifact I've generated in a specific folder, 
call it destination folder.
But, when the size of my ear is more than 20Mo, the size is multiplied by 2 
in the destination folder.
I thought that it just makes a copy.
I'm searching some help to solve this problem, do you have any idea ?
I don't understand why this behavior happens.

Cheers,

_
Vincent LE SQUERE | Capgemini Ouest | ITC Nantes
vincent.lesqu...@capgemini.com
Office: +33(0)251 173 501
Join the Collaborative Business Experience
_

This 
message contains information that may be privileged or confidential and is the 
property of the Capgemini Group. It is intended only for the person to whom it 
is addressed. If you are not the intended recipient, you are not authorized to 
read, print, retain, copy, disseminate, distribute, or use this message or any 
part thereof. If you receive this message in error, please notify the sender 
immediately and delete all copies of this message.

Maven Exec - Inheritance - Multi Module Build

[jabba]

Hi,

i'm testing a setup with Maven and a combination of Java/Non Java Projects
(using RPM plugin etc.)...

I'm using a parent to bind some calls to exec plugin to particular phases:


   
  
   org.codehaus.mojo
exec-maven-plugin
1.1.1


initialize
initialize

exec


cmake


.







org.codehaus.mojo
exec-maven-plugin
1.1.1


compile
compile

exec


make




   

...
Using the rpm-plugin in modules is working like a charm...so far so good

but now i reached a little problem, cause i have a piling project which does
not need any calls to the above exec parts...but based on my configuration
they are of course called as defined

Is there a way to prevent calling the exec's in a sub-module which inherits
the parent pom information

Kind regards
Karl Heinz Marbaise
-- 
View this message in context: 
http://old.nabble.com/Maven-Exec---Inheritance---Multi-Module-Build-tp26779913p26779913.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Error using element in

[Matthew Adams]

Duh.  My bad.  I figured it had to be something simple.  Thanks!

On Mon, Dec 14, 2009 at 7:10 AM, Justin Edelson  wrote:
> It needs to be
> 
> *  *
>    
>         org.datanucleus
>         datanucleus-core
>         2.0.0-m4
>    ...more...
>    
>  * *
> 
>
> See
> http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_dependencyManagement
>
> 
> Justin
>
> On Mon, Dec 14, 2009 at 10:03 AM, Matthew Adams 
> wrote:
>
>> Hi all,
>>
>> I'm trying to support different JPA implementations in my build.
>>
>> According to
>> http://maven.apache.org/guides/introduction/introduction-to-profiles.html,
>> I can specify the  element in a build profile.
>> However, when I do, I get a POM parse error with the following error
>> reason:
>>
>> Reason: Parse error reading POM. Reason: Unrecognised tag:
>> 'dependency' (position: START_TAG seen
>> ...\r\n\t\t\t\t... @329:17)  for
>> project
>>
>> Here's the relevant portion from my root pom:
>>
>>            
>>                
>>                        datanucleus
>>                        
>>                                true
>>                        
>>                        
>>                                datanucleus
>>                        
>>                        
>>                                
>>                                        org.datanucleus
>>
>>  datanucleus-core
>>                                        2.0.0-m4
>>                                
>>                                ...
>>                        
>>                
>>                ...
>>
>> What am I doing wrong?
>>
>> Thanks in advance,
>> Matthew
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
mailto:matt...@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadam...@gmail.com
msn:matt...@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Error using element in

[Justin Edelson]

It needs to be

*  *

 org.datanucleus
 datanucleus-core
 2.0.0-m4
...more...

 * *


See
http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_dependencyManagement


Justin

On Mon, Dec 14, 2009 at 10:03 AM, Matthew Adams wrote:

> Hi all,
>
> I'm trying to support different JPA implementations in my build.
>
> According to
> http://maven.apache.org/guides/introduction/introduction-to-profiles.html,
> I can specify the  element in a build profile.
> However, when I do, I get a POM parse error with the following error
> reason:
>
> Reason: Parse error reading POM. Reason: Unrecognised tag:
> 'dependency' (position: START_TAG seen
> ...\r\n\t\t\t\t... @329:17)  for
> project
>
> Here's the relevant portion from my root pom:
>
>
>
>datanucleus
>
>true
>
>
>datanucleus
>
>
>
>org.datanucleus
>
>  datanucleus-core
>2.0.0-m4
>
>...
>
>
>...
>
> What am I doing wrong?
>
> Thanks in advance,
> Matthew
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Error using element in

[Matthew Adams]

Hi all,

I'm trying to support different JPA implementations in my build.

According to 
http://maven.apache.org/guides/introduction/introduction-to-profiles.html,
I can specify the  element in a build profile.
However, when I do, I get a POM parse error with the following error
reason:

Reason: Parse error reading POM. Reason: Unrecognised tag:
'dependency' (position: START_TAG seen
...\r\n\t\t\t\t... @329:17)  for
project

Here's the relevant portion from my root pom:



datanucleus

true


datanucleus



org.datanucleus

datanucleus-core
2.0.0-m4

...


...

What am I doing wrong?

Thanks in advance,
Matthew

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Howto configure Logging format of Maven3 console output

[Volkmar Nissen]

Hi,

I want to change the format of the console output in order to get timestamps 
for each logging entry.
The only information I found (http://jira.codehaus.org/browse/MNG-519) with 
respect to this issue is for maven 2 and does not match to maven 3.

How can the logging format been changed in maven3?
Where are the logging configuration files?

Thank you,

Volkmar


-- 
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

AW: pom.xml : element

[Mark Struberg]

the  element in the pom is used for every SCM action in maven, e.g. if you 
do a mvn release:prepare / mvn release:perform and stuff.

Since Hudson and other CI environments often do not rely on the build system 
for updating the project, they have the ability to do this their self (otoh, 
some CI systems do use maven-scm internally, but get the scm URL parameter from 
the UI rather than the pom.

LieGrue,
strub

--- Rémy  schrieb am Mo, 14.12.2009:

> Von: Rémy 
> Betreff: pom.xml :  element
> An: users@maven.apache.org
> Datum: Montag, 14. Dezember 2009, 10:41
> 
> Hello,
> 
> What is the purpose of the  element defined in
> the pom.xml. I can't
> understand its usefulness.
> In Hudson, the link to the SCM is configured in the job.
> When I make a
> release (maven-release-plugin), I feel that the plugin is
> based on
> information contained in the workspace.
> 
> http://maven.apache.org/pom.html#SCM http://maven.apache.org/pom.html#SCM 
> 
> Thank you.
> 
> Remy
> 
> 
> -- 
> View this message in context: 
> http://old.nabble.com/pom.xml-%3A-%3Cscm%3E-element-tp26775153p26775153.html
> Sent from the Maven - Users mailing list archive at
> Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 

__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: pom.xml : element

[Anders Hammar]

Mainly it's used by maven-scm-plugin and maven-release-plugin. Or any other
plugin that uses this metadata. The POM is all about describing a project.
This info/metadata can then be used by any plugin or tool. For instance, the
scm info is also used by M2Eclipse if you want to checkout a project based
on the scm info of a pom.xml.

/Anders

On Mon, Dec 14, 2009 at 10:41, Rémy  wrote:

>
> Hello,
>
> What is the purpose of the  element defined in the pom.xml. I can't
> understand its usefulness.
> In Hudson, the link to the SCM is configured in the job. When I make a
> release (maven-release-plugin), I feel that the plugin is based on
> information contained in the workspace.
>
> http://maven.apache.org/pom.html#SCM http://maven.apache.org/pom.html#SCM
>
> Thank you.
>
> Remy
>
>
> --
> View this message in context:
> http://old.nabble.com/pom.xml-%3A-%3Cscm%3E-element-tp26775153p26775153.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

pom.xml : element

[Rémy]

Hello,

What is the purpose of the  element defined in the pom.xml. I can't
understand its usefulness.
In Hudson, the link to the SCM is configured in the job. When I make a
release (maven-release-plugin), I feel that the plugin is based on
information contained in the workspace.

http://maven.apache.org/pom.html#SCM http://maven.apache.org/pom.html#SCM 

Thank you.

Remy


-- 
View this message in context: 
http://old.nabble.com/pom.xml-%3A-%3Cscm%3E-element-tp26775153p26775153.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: modules are built but not copied to local repository?

[Anders Hammar]

Executing mvn install gives me this:

[INFO] Building examples in J2ME with juliac
[INFO]

[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO]

[INFO] Building COSMOS Helloworld example for J2ME/CLDC
[INFO]

[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] A required plugin was not found: Plugin could not be found - check
that the goal name is correct: Unable to download the artifact from any
repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=cosmos-me
-DartifactId=cosmos-me-plugin -Dversion=0.1.8-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=cosmos-me -DartifactId=cosmos-me-plugin
-Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file
-Durl=[url] -DrepositoryId=[id]


  cosmos-me:cosmos-me-plugin:maven-plugin:0.1.8-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


  cosmos-me:cosmos-me-plugin:maven-plugin:0.1.8-SNAPSHOT

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


This is my nevironment:
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.5.0_15
Java home: C:\Program Files\Java\jdk1.5.0_15\jre
Default locale: sv_SE, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

Sorry, I give up.

/Anders

PS. The earlier NPE I mentioned was when building with Maven 3.0-alpha-5.
Try it for yourself; either there's a bug in Maven 3.0 or something weird in
your project(s).

On Mon, Dec 14, 2009 at 08:39, Anders Hammar  wrote:

> Kinh,
>
> When doing mvn clean, I get a message about a missing plugin:
> [INFO] A required plugin was not found: Plugin could not be found - check
> that the goal name is correct: Unable to download the artifact from any
> repository
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=cosmos.distribution.deployment
> -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=cosmos.distribution.deployment
> -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>   cosmos.distribution.deployment:fdf-plugin:maven-plugin:0.1.8-SNAPSHOT
>
> Where is that plugin? Some repo I need to configure in my settings.xml?
>
> /Anders
>
>
> On Fri, Dec 11, 2009 at 17:48, NGUYEN Cong Kinh <
> cong_kinh.ngu...@it-sudparis.eu> wrote:
>
>> Please send this error to me.  Because I haven't seen it. Thank you.
>>
>>
>> Kinh
>>
>> Anders Hammar a écrit :
>>
>>> After checking out and building for ages I get a NPE in helloworld ex
>>> 1...
>>>
>>> /Anders
>>>
>>> On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh <
>>> cong_kinh.ngu...@it-sudparis.eu> wrote:
>>>
>>>
>>>
 In fact, in the trunk/B, there are some modules, for example B1 & B2,
 but
 B2 uses B1 as the dependency. When executing the command "mvn clean
 install"
 for B2, Maven finds the dependency B1, but it is not located in local
 repository. Therefore, there's an error "missing artifact...". You can
 check
 at
 svn co svn+ssh://gu...@picoforge.int-evry.fr/cosmos/trunk
 with "guest" as password (twice for entering password)

 Kinh

 Anders Hammar a écrit :

  What does the build output say - any errors?


> /Anders
>
> On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh <
> cong_kinh.ngu...@it-sudparis.eu> wrote:
>
>
>
>
>
>> Hello everybody,
>>
>> I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation
>> by
>> Maven. In fact, for example I have the following structure:
>>
>> - trunk
>> + pom.xml
>> +-- A
>>  + pom.xml
>>  +-- A1
>> + pom.xml
>> +-- A11
>>  ...
>> +-- A12
>> ...
>>  +-- A2
>>  +-- A3
>> +-- B
>>  +-- B1
>>
>> In the trunk, I execute the "mvn clean install" (before executing this
>> command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A
>> are
>> copied to ~/.m2/repository. The other modules in trunk/B, they
>> compiled
>> to
>> target/..., but they aren't copied to ~/.m2/repository.
>>
>>
>> I

Re: SOLVED I guess. Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?

[Baptiste MATHUS]

Please never change the subject. It appears as a new thread, and if someone
finds the original entry, he won't see this one in the end...

Thanks.

2009/12/12 Rick R 

> After more googling I found this discussion
>
> http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-maven-plugin-3.x.htmlwhere
> others had the same issue. Apparently jdom is needed in your maven lib
> if a certain dependency relies on it. Something with plexus was bitching
> about it but no idea what that was about. Seems really bad though that
> someone would have to manually add that jar to the maven lib so I'd like to
> get the root cause of thatissue at some point. Apparently in the older
> maven
> projects it was part of the uber-jar?
>
> I need a drink now for all the time wasted on this today:) I had tried
> adding a dependency to the pom for the jdom jar (actually that was one of
> the first things I did), but that didn't help. I wouldn't have thought that
> it was needed in the actual lib dir.
>
> (Now a crazier question though is why would my old repo have worked though
> without adding this jar? I'm too tired to try to figure that one out.)
>
> On Fri, Dec 11, 2009 at 7:51 PM, Rick R  wrote:
>
> >
> >
> > On Fri, Dec 11, 2009 at 6:37 PM, Rick R  wrote:
> >
> >>
> >> Now to add to the confusion, not sure it's the firewall at all ... on
> the
> >> Mac and Windows machine both behind company firewall...the Mac now gives
> the
> >> errors like:
> >>
> >>
> >> [INFO]
> >> 
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> 
> >> [INFO] Failed to resolve artifact.
> >>
> >> Missing:
> >> --
> >> 1) com.adobe.flex:compiler:pom:3.2.0.3958
> >>   Path to dependency:
> >> 1)
> >> org.sonatype.flexmojos:flexmojos-maven-plugin:maven-plugin:3.4.2
> >> 2) com.adobe.flex:compiler:pom:3.2.0.3958
> >>
> >>
> >>
> > For what it's worth I got past my recent errors by changing the
> repository
> > http://repository.sonatype.org/content/groups/public/
> >
> > Now the project that I provided earlier that was zipped up builds, but I
> > still have the issue in my current project related to the below. But I'll
> > work now on debugging better since the archetype works it must be
> something
> > conflicting in my code causing an issue. Still really odd my old repo
> works
> > with the same code base though. That part has me really stumped.
> >
> >
> > [WARNING] Not defined if locales should be merged or not
> > [WARNING] Unable to find license.jar on classpath. Check wiki for
> > instructions about how to add it:
> >https://docs.sonatype.org/display/FLEXMOJOS/FAQ#FAQ-1.3
> > [FATAL ERROR] org.sonatype.flexmojos.compiler.LibraryMojo#execute()
> caused
> > a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date.
> > Check the realms:
> > [FATAL ERROR] Plugin realm =
> > app0.child-container[org.sonatype.flexmojos:flexmojos-maven-plugin:3.4.2]
> > 
> > urls[93] =
> >
> file:/Users/rick/.m2/repository/org/apache/maven/shared/maven-plugin-testing-harness/1.1/maven-plugin-testing-harness-1.1.jar
> >
> > [FATAL ERROR] Container realm = plexus.core
> > urls[0] = file:/Users/rick/java/maven/lib/maven-2.2.1-uber.jar
> > [INFO]
> > 
> > [ERROR] FATAL ERROR
> > [INFO]
> > 
> > [INFO] org/jdom/input/SAXBuilder
> > org.jdom.input.SAXBuilder
> > [INFO]
> > 
> > [INFO] Trace
> > java.lang.NoClassDefFoundError: org/jdom/input/SAXBuilder
> > at
> >
> org.sonatype.flexmojos.utilities.FDKConfigResolver.getConfig(FDKConfigResolver.java:95)
> >
> >
>
>
>
> --
> Rick R
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !