Fmota Tech

Hi,

I have a flat project layout, with one parent(parent-flat) and two modules (module1-flat and module2-flat).

In my parent’s pom, I have : ../module1-flat ../module2-flat + scm connection

For each modules, I just have : parent-flat mygroupid 0.0.1-SNAPSHOT module1-flat

My SVN structure looks like this : – branches – tags – trunk |-flat-multimodules |- module1-flat |- module2-flat |- parent-flat

To make a release, I have to do mvn release:prepare -DcommitByProject=true (if I ommit commitByProject, it doesn’t work) Then a mvn:release perform

I obtain in SVN : – branches – tags |-parent-flat-0.0.1 |- module1-flat |- module2-flat |- parent-flat – trunk |-flat-multimodules |- module1-flat |- module2-flat |- parent-flat

If I want to do a mvn release:rollback, I have the following error message : ERROR] BUILD FAILURE [INFO]

I’m trying to access the project.build.directory property which is defined in my pom as

${project.basedir}/target ….

In ant I have this setup:

However when I run my ant build, outputdir is being set to the literal value “${project.basedir}/target” rather than antrun expanding the variable ${project.basedir}. Has anyone else run into this issue?

What does reloading a plug-in container mean in maven? This happens in just a single machine, every other machine seems to be fine. How do I fix this issue?

[INFO] Reloading plugin container for: org.apache.maven.plugins:m aven-clean-plugin:2.4.1. The plugin artifact has changed. [INFO] [clean:clean {execution: default-clean}] [INFO] Reloading plugin container for: org.codehaus.mojo:versions -maven-plugin:1.2. The plugin artifact has changed. [INFO] Reloading plugin container for: org.apache.maven.plugins:m aven-compiler-plugin:2.3.1. The plugin artifact has changed. [INFO] Reloading plugin container for: org.apache.maven.plugins:m aven-jar-plugin:2.3.1. The plugin artifact has changed. [INFO] Reloading plugin container for: org.apache.maven.plugins:m aven-clean-plugin:2.4.1. The plugin artifact has changed. [INFO] Reloading plugin container for: org.apache.maven.plugins:m aven-site-plugin:2.1.1. The plugin artifact has changed. [INFO] Reloading plugin container for: org.apache.maven.plugins:m

aven-install-plugin:2.3.1. The plugin artifact has changed. [INFO] [site:attach-descriptor {execution: default-attach-descrip…

Why aren’t you checking the project out in Eclipse?

BTW. I suggest using the STS version of Eclipse since all your plug-ins come preinstalled except for Subversion which is mostly included.

On 13/07/2010 11:31 AM, Bahadýr Konu wrote:

on

Hi Julien,

yes, I tried that too and it does not work. task1 does not get executed

regards,

Wim

2010/7/13 Julien HENRY

Hi,

I need to run the antrun plugin twice in the packaging phase. I found this on the wiki: http://docs.codehaus.org/display/MAVENUSER/MiniGuide-AntMultiPhase

However, it speaks of different lifecycle phases. I tried with the same phase and that works, however, I need to run another plugin in between. Is this possible?

I was hoping that all plugins’ executions would be sorted by their id. That way, i could use id’s like ‘step-1-do-something’, ‘step-2-do-something-else’, to force a certain order of plugin execution.

regards,

Wim

I have been unable to get the struts convention plugin to work on JBoss 5.1.

If I set

as per the convention plugin documentation, and debug through the setup code, I notice that the WEB-INF/classes directory in my war (which is deployed in an ear) gets removed from the set of URL’s to search for action classes.

Switching that constant to ‘false’ allows the WEB-INF/classes directory to remain in the set of URL’s, but then I get this error when it attempts to load the war:

2010-07-09 22:14:03,102 ERROR [CommonsLogger.java:27] : Unable to read URL [vfszip://server/default/deploy/myapp.ear/myapp- web.war/WEB-INF/classes/] java.io.FileNotFoundException: //server/default/ deploy/myapp.ear/myapp-web.war/WEB-INF/classes at org .jboss .net.protocol.file.FileURLConnection.connect(FileURLConnection.java:105) at org .jboss .net .protocol.file.FileURLConnection.getInputStream(FileURLConnection.java: 112) at java.net.URL.openStream(URL.java:1007) at com.opensymphony.xwork2.util.finder.ClassFinder.jar(ClassFinder.java: 464) at com .opensymphony.xwork2.util.finder.ClassFinder.(ClassFinder.java: 129) at org .apache .struts2 .convention .PackageBasedActionConfigBuilder .findActions(PackageBasedActionConfigBuilder.java:352) at org .apache .struts2 .convention .PackageBasedActionConfigBuilder .buildActionConfigs(PackageBasedActionConfigBuilder.java:317) at org .apache .struts2 .convention .ClasspathPackageProvider.loadPackages(ClasspathPackageProvider.java:53)

Is there some magical configuration setting I am missing? or does this just not work on JBoss 5.1 when deploying inside of an ear?

Thanks,

Scott

I’m also using a flat structure.

I found that the keys to making this work seem to be:

1) use release 2.0 of the release plugin. This is the release with the support for “flat” hierarchies. Note that the Apache common parent POM version 7 (the latest) still doesn’t specify this release, it specifies an earlier one (2.0-beta-9) which doesn’t have this support, so you have to override that – if you’re using the Apache common parent pom (i.e. http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom ).

2) in each pom in the flat hierarchy, insure the element is pointing to the right place in your SVN or whatever. If you let these “inherit” from parent poms, the inheritance makes often wrong assumptions that the children of the parent are located underneath the parent pom directory. Specifying the actual location overrides this behavior.

-Marshall Schor

On 7/9/2010 11:28 AM, DeGrande, Rick wrote:

Dear All,

is it possible to include system-scoped dependencies in a shaded jar? My dependencies look like this:

jboss-stuff jbossall-client 5.1 system ${jbosshome}/client/jbossall-client.jar

I’ve tried adding

jboss-stuff:*

but the contents of jbossall-client.jar still don’t get included in the shaded jar.

Am I just making a stupid mistake? Or are system-scoped dependencies always excluded from shaded jars?

Best regards, Jan

Quick question: I noticed that webResources section to include something in a war via parent pom fails to execute. The webResources section is omitted during execution. Copying the same section to a the actual pom war works just fine. Is it by design or a bug?

More often than not I have to include an xmi file. Location of the file is dictated by another tool. I thought that I could save some typing and include the file in the parent pom. I tried all recent versions of the war plugin to no avail.

Also I remember a discussion on this forum regarding overlays. Is overlay a suitable solution?

Thanks, Dave