Re: Maven 3 explode goal?
I see everyone ranting on about producing a fully exploded ear AFAIK, maven already supports doing that (with the caviat that the unexploded war will have to be produced for each war module [because you need to be able to store it in the local/remote repo's] If you don't produce a war file as part of your build then you will have to build the exploded war _every build_. By exploding the .war file into the .ear you have the choice of only building the .ear module and using the .war from your local repo] In any case, to have an exploded .ear, you either just have to specify the unpacktrue/unpack option for each of the modules in your ear in the m-ear-p configuration section, or you configure the unpackTypes option, e.g. project [...] build [...] plugins [...] plugin artifactIdmaven-ear-plugin/artifactId version2.4.2/version configuration unpackTypesjar,rar,war/unpackTypes /configuration /plugin [...] /plugins [...] /build [...] /project - Stephen On 7 July 2010 21:56, Wayne Fay wayne...@gmail.com wrote: Well after some extensive experimentation with creating a custom lifecycle, it appears as though using war:explode in components.xml with packagingwar/packaging in the POM may not be possible. As I understand it, this is correct because Maven already has a pre-defined lifecycle for projects of type war. You could potentially produce a fully-customized build of Maven that did not contain the pre-defined war packaging lifecycle, but I wouldn't want to be involved in supporting it and mandating your developers to use it instead of the usual Maven distribution etc. When I use packagingexploded/packaging, it works ok. But I don't think this is feasible to use for a WAR project and not sure how to do this for a EAR project (which contains one or more WARs). You would probably need to produce both exploded-war and exploded-ear packaging types and corresponding custom lifecycles. You may also find this webpage to be helpful, if you haven't already been reading it: http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/ Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven release plugin not updating sub-module dependencies
Hello, Rick.
Please, clarify, how do you define submodule dependency?
Do you use dependecyManagement section in parent pom with
${project.version} property?
Best regards,
Aleksey Didik.
08.07.2010 2:34, DeGrande, Rick пишет:
I have a multi--module configuration. the directory structure is:
aggregate
ejb
war
The war file includes the ejb as a dependency. When I do a
release:prepare -DdryRun maven generates the pom.xml.tag correctly but
it doesn't update the sub module dependencies in the pom.xml.next. How
do I get it to update the sub-module dependencies ?
thanks
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Finding out the dependencies of an (arbitrary) artifact
Hi, I thought this would be a no brainer, but suprisingly I found no answer to this so far: How can I find out the dependencies of an arbitrary artifact (say org.sonatype.tycho:tycho-compiler-jdt)? BTW: yes, I know there's a workaround: Add it as a dependency to a POM and run mvn dependency:tree But I thought there would be an easier way. Christoph - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Finding out the dependencies of an (arbitrary) artifact
Hello Christoph, Try to use mvnrepositry.com. For example: http://mvnrepository.com/artifact/org.sonatype.tycho/tycho-compiler-jdt/0.9.0 HTH, Aleksey Didik. 08.07.2010 11:20, Christoph Kutzinski пишет: Hi, I thought this would be a no brainer, but suprisingly I found no answer to this so far: How can I find out the dependencies of an arbitrary artifact (say org.sonatype.tycho:tycho-compiler-jdt)? BTW: yes, I know there's a workaround: Add it as a dependency to a POM and run mvn dependency:tree But I thought there would be an easier way. Christoph - 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
Re: Write Maven Books - Packt Publishing
Am Mittwoch, 7. Juli 2010 15:48:29 schrieb Ron Wheeler: On 07/07/2010 8:55 AM, Martin Höller wrote: Hi Ron! Am Mittwoch, 7. Juli 2010 14:00:22 schrieb Ron Wheeler: On 07/07/2010 5:19 AM, Benjamin Wootton wrote: Would anyone be interested in teaming up on something like this? Have thought about pitching a maven book before but don't have the cycles to go it alone There is a desperate need for a Best Practice book. There is one already from Brett Porter and Maria Odea Ching: https://www.packtpub.com/apache-maven-2-effective-implementations/book I'd say it's a fairly good book. hth, - martin Is it a How-to book or a Best Practice book. Kind of a mix. It uses a single app to show you how to accomplish things and it uses best practices to do so. Quite often it does not dive too deep into the subject but therefore you get a good overview very quickly. Actually I didn't read the whole book yet, but read the first few chapters and use it as a reference for special problems that arise. hth, - martin signature.asc Description: This is a digitally signed message part.
Re: Creating a Custom Lifecycle
Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian: There is some limited coverage of creating a custom lifecycle here: http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-cu stom-lifecycle.html but it also covers forking and parallel lifecycles, I'm not sure I'm really interested in that. I want to change the package lifecycle so that it uses war:explode goal rather than war:war goal. What about just configuring the war:explode goal in your pom.xml? war:war would still be executed, but is this a problem? hth, - martin signature.asc Description: This is a digitally signed message part.
Re: Finding out the dependencies of an (arbitrary) artifact
Thanks Aleksey, this works. However, I also want to know the concrete versions of the dependencies (in my environment) and mvnrepository.com doesn't give me that. Christoph Original-Nachricht Datum: Thu, 08 Jul 2010 11:29:12 +0400 Von: Aleksey Didik di...@magenta-technology.ru An: Maven Users List users@maven.apache.org Betreff: Re: Finding out the dependencies of an (arbitrary) artifact Hello Christoph, Try to use mvnrepositry.com. For example: http://mvnrepository.com/artifact/org.sonatype.tycho/tycho-compiler-jdt/0.9.0 HTH, Aleksey Didik. 08.07.2010 11:20, Christoph Kutzinski пишет: Hi, I thought this would be a no brainer, but suprisingly I found no answer to this so far: How can I find out the dependencies of an arbitrary artifact (say org.sonatype.tycho:tycho-compiler-jdt)? BTW: yes, I know there's a workaround: Add it as a dependency to a POM and run mvn dependency:tree But I thought there would be an easier way. Christoph - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
JBoss ESB in public Maven repo?
Hi! Does anybody know if JBoss ESB 4.x dependencies are available in any public Maven repo? All I have found is a few references from 2008 stating that they are not available when asking Google. Browsing http://repository.jboss.com/maven2 http://snapshots.jboss.org/maven2 haven't given me anything useful. /Thomas -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JBoss ESB in public Maven repo?
Thomas, Check out JBoss new maven 2 repos hosted by Nexus: https://repository.jboss.org/nexus/ I did find some jbossesb* artifacts, but if you have a specific class you could search for that. There are also some blog posts and wiki pages on the net describing JBoss's new repos. /Anders On Thu, Jul 8, 2010 at 13:18, Thomas Sundberg t...@kth.se wrote: Hi! Does anybody know if JBoss ESB 4.x dependencies are available in any public Maven repo? All I have found is a few references from 2008 stating that they are not available when asking Google. Browsing http://repository.jboss.com/maven2 http://snapshots.jboss.org/maven2 haven't given me anything useful. /Thomas -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: JBoss ESB in public Maven repo?
Hi! Thanks a lot Anders! You put me in the right direction. The jar I was looking for is available at https://repository.jboss.org/nexus/content/groups/public-jboss/org/jboss/soa/bpel/dependencies/esb/jbossesb-rosetta/4.8/ /Thomas On Thu, Jul 8, 2010 at 13:25, Anders Hammar and...@hammar.net wrote: Thomas, Check out JBoss new maven 2 repos hosted by Nexus: https://repository.jboss.org/nexus/ I did find some jbossesb* artifacts, but if you have a specific class you could search for that. There are also some blog posts and wiki pages on the net describing JBoss's new repos. /Anders On Thu, Jul 8, 2010 at 13:18, Thomas Sundberg t...@kth.se wrote: Hi! Does anybody know if JBoss ESB 4.x dependencies are available in any public Maven repo? All I have found is a few references from 2008 stating that they are not available when asking Google. Browsing http://repository.jboss.com/maven2 http://snapshots.jboss.org/maven2 haven't given me anything useful. /Thomas -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven release plugin not updating sub-module dependencies
No, I was thinking about doing that, but I have the dependencies in the sibling
poms. I'm not using the ${project.version} in these poms. I just have the
SNAPSHOT version specified on the sibling dependencies.
Thanks
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 1:14 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello, Rick.
Please, clarify, how do you define submodule dependency?
Do you use dependecyManagement section in parent pom with
${project.version} property?
Best regards,
Aleksey Didik.
08.07.2010 2:34, DeGrande, Rick пишет:
I have a multi--module configuration. the directory structure is:
aggregate
ejb
war
The war file includes the ejb as a dependency. When I do a
release:prepare -DdryRun maven generates the pom.xml.tag correctly but
it doesn't update the sub module dependencies in the pom.xml.next. How
do I get it to update the sub-module dependencies ?
thanks
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven release plugin not updating sub-module dependencies
Hello Rick.
In this case release will not change dependencies versions, because
maven have no difference between external artifact and module artifact.
My suggestion is to use ${project.version} and dependencyManagement
for cross module dependencies.
hth,
Aleksey Didik.
08.07.2010 17:59, DeGrande, Rick пишет:
No, I was thinking about doing that, but I have the dependencies in the sibling
poms. I'm not using the ${project.version} in these poms. I just have the
SNAPSHOT version specified on the sibling dependencies.
Thanks
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 1:14 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello, Rick.
Please, clarify, how do you define submodule dependency?
Do you usedependecyManagement section in parent pom with
${project.version} property?
Best regards,
Aleksey Didik.
08.07.2010 2:34, DeGrande, Rick пишет:
I have a multi--module configuration. the directory structure is:
aggregate
ejb
war
The war file includes the ejb as a dependency. When I do a
release:prepare -DdryRun maven generates the pom.xml.tag correctly but
it doesn't update the sub module dependencies in the pom.xml.next. How
do I get it to update the sub-module dependencies ?
thanks
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
-
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
RE: maven release plugin not updating sub-module dependencies
Aleksey,
I thought it would update the sibling modules based on the modules included in
the parent pom. It updates the sibling dependencies when it changes the tagged
version just not the next version.
So you're saying move the sibling dependencies to the dependencyManagement and
use ${project.version}, or just use ${project.version} in the sibling poms
instead of using the X.X-SNAPSHOT version ??
Thanks for your response
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 8:12 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello Rick.
In this case release will not change dependencies versions, because
maven have no difference between external artifact and module artifact.
My suggestion is to use ${project.version} and dependencyManagement
for cross module dependencies.
hth,
Aleksey Didik.
08.07.2010 17:59, DeGrande, Rick пишет:
No, I was thinking about doing that, but I have the dependencies in the
sibling poms. I'm not using the ${project.version} in these poms. I just
have the SNAPSHOT version specified on the sibling dependencies.
Thanks
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 1:14 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Hello, Rick.
Please, clarify, how do you define submodule dependency?
Do you usedependecyManagement section in parent pom with
${project.version} property?
Best regards,
Aleksey Didik.
08.07.2010 2:34, DeGrande, Rick пишет:
I have a multi--module configuration. the directory structure is:
aggregate
ejb
war
The war file includes the ejb as a dependency. When I do a
release:prepare -DdryRun maven generates the pom.xml.tag correctly but
it doesn't update the sub module dependencies in the pom.xml.next. How
do I get it to update the sub-module dependencies ?
thanks
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
-
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
Re: maven release plugin not updating sub-module dependencies
Rick, see comments below.
I thought it would update the sibling modules based on the modules included in
the parent pom. It updates the sibling dependencies when it changes the tagged
version just not the next version.
Look like I've not clear understood release process with sibling
dependencies. If it updates when it changes the tagged version, but not
updates next version, it looks like an issue...
So you're saying move the sibling dependencies to the dependencyManagement and
use ${project.version}, or just use ${project.version} in the sibling poms
instead of using the X.X-SNAPSHOT version ??
By the way, I use ${project.version}-dependencyManagement way in all
my projects and it's fully cover all necessities.
If you will use ${project.version} instead of using X.X-SNAPSHOT
version, it could make some troubles, because ${project.version}
property for current pom (module) is this module version. And if you
associate dependency version with current module version/ it could be
not good.
I use this way:
*parent pom.xml:*
version 1.0-SNAPSHOT /version
/modules
modulea-module/module
moduleb-module/module
/modules
dependencyManagement
dependencies
dependency
groupId.../groupId
artifactIda-module/artifactId
version${project.version}/version
/dependency
dependencies
/dependencyManagement/
*b-module pom.xml:*
/ dependencies
dependency
groupId.../groupId
artifactIda-module/artifactId
/dependency
dependencies/
In this variant I'm using the same version for all modules in my project
and all sibling modules depends on each other by project version of
parent module.
Release plugin update only module version, not dependency versions. All
dependency versions will be updated automatically by using
dependencyManagement section and ${project.version} property.
It's usable in most projects, than have no necessity to have different
versions of project modules.
In this case also usable to set
/autoVersionSubmodulestrue/autoVersionSubmodules/ in release plugin
configuration.
It help you to input release and next version only for parent module,
sibling modules will use the same version.
Hope this help,
Aleksey.
Re: Creating a Custom Lifecycle
Martin Höller wrote:
Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian:
There is some limited coverage of creating a custom lifecycle here:
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-cu
stom-lifecycle.html
but it also covers forking and parallel lifecycles, I'm not sure I'm
really
interested in that. I want to change the package lifecycle so that it
uses
war:explode goal rather than war:war goal.
What about just configuring the war:explode goal in your pom.xml? war:war
would still be executed, but is this a problem?
hth,
- martin
I just realized something very basic after reading first chapter of Maven 2:
Effective Implementation. The web application archive is produced in the
target directory, which is Maven's default working directory. There you
will find both the target/simple-webapp subdirectory that contains the
exploded, or unpacked, web application contents ready to be packaged, and
the target/simple-webapp.war file that contains those files after the
packaging process.
So perhaps if the unpack goal of the jboss-maven-plugin was modified to use
the already exploded WAR in the exploded EAR, then we would be good. At
least as far as JBoss users are concerned...
public void unpack( File zipFile, File targetDir )
throws IOException
{
FileInputStream in = new FileInputStream( zipFile );
ZipInputStream zipIn = new ZipInputStream( in );
File dir = targetDir.getCanonicalFile();
dir.mkdirs();
ZipEntry entry;
while ( ( entry = zipIn.getNextEntry() ) != null )
{
if ( entry.isDirectory() )
{
continue;
}
String file = targetDir + / + entry.getName();
new File( file ).getParentFile().getCanonicalFile().mkdirs();
FileOutputStream out = new FileOutputStream( file );
streamcopy( zipIn, out );
out.close();
}
zipIn.close();
}
http://svn.codehaus.org/mojo/tags/jboss-maven-plugin-1.4.1/src/main/java/org/codehaus/mojo/jboss/HardDeployMojo.java
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045103.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 release plugin not updating sub-module dependencies
Aleksey,
Thank you for the advice. That looks like it will work much better than what I
was doing.
Rick
-Original Message-
From: Aleksey Didik [mailto:di...@magenta-technology.ru]
Sent: Thursday, July 08, 2010 9:13 AM
To: Maven Users List
Subject: Re: maven release plugin not updating sub-module dependencies
Rick, see comments below.
I thought it would update the sibling modules based on the modules included
in the parent pom. It updates the sibling dependencies when it changes the
tagged version just not the next version.
Look like I've not clear understood release process with sibling
dependencies. If it updates when it changes the tagged version, but not
updates next version, it looks like an issue...
So you're saying move the sibling dependencies to the dependencyManagement
and use ${project.version}, or just use ${project.version} in the sibling
poms instead of using the X.X-SNAPSHOT version ??
By the way, I use ${project.version}-dependencyManagement way in all
my projects and it's fully cover all necessities.
If you will use ${project.version} instead of using X.X-SNAPSHOT
version, it could make some troubles, because ${project.version}
property for current pom (module) is this module version. And if you
associate dependency version with current module version/ it could be
not good.
I use this way:
*parent pom.xml:*
version 1.0-SNAPSHOT /version
/modules
modulea-module/module
moduleb-module/module
/modules
dependencyManagement
dependencies
dependency
groupId.../groupId
artifactIda-module/artifactId
version${project.version}/version
/dependency
dependencies
/dependencyManagement/
*b-module pom.xml:*
/ dependencies
dependency
groupId.../groupId
artifactIda-module/artifactId
/dependency
dependencies/
In this variant I'm using the same version for all modules in my project
and all sibling modules depends on each other by project version of
parent module.
Release plugin update only module version, not dependency versions. All
dependency versions will be updated automatically by using
dependencyManagement section and ${project.version} property.
It's usable in most projects, than have no necessity to have different
versions of project modules.
In this case also usable to set
/autoVersionSubmodulestrue/autoVersionSubmodules/ in release plugin
configuration.
It help you to input release and next version only for parent module,
sibling modules will use the same version.
Hope this help,
Aleksey.
-
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
Checksum problem with mysql.mysql-connector-java.1.5.13
Hi, It seems there are somes problems with artifact and checksum in Maven repo for mysql.mysql-connector-java.1.5.13 (http://repo1.maven.org/maven2//mysql/mysql-connector-java/5.1.13/) The md5 and sha1 files should be : mysql-connector-java-5.1.13.jar.md5 and mysql-connector-java-5.1.13.jar.sha1 instead of mysql-connector-java-5.1.13.md5 and mysql-connector-java-5.1.13.sha1 (jar extension missed). Best regards, Vincent Hardion - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Checksum problem with mysql.mysql-connector-java.1.5.13
It seems there are somes problems with artifact and checksum in Maven repo for mysql.mysql-connector-java.1.5.13 Problems with the content of the repository should be reported in Jira under the MEV project: http://jira.codehaus.org/browse/MEV You should also open a bug/ticket with the mysql-connector folks so they know about and are involved in resolving the issue. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Creating a Custom Lifecycle
On 7/8/10 11:28 AM, asookazian wrote: I just realized something very basic after reading first chapter of Maven 2: Effective Implementation. The web application archive is produced in the target directory, which is Maven's default working directory. There you will find both the target/simple-webapp subdirectory that contains the exploded, or unpacked, web application contents ready to be packaged, and the target/simple-webapp.war file that contains those files after the packaging process. So perhaps if the unpack goal of the jboss-maven-plugin was modified to use the already exploded WAR in the exploded EAR, then we would be good. At least as far as JBoss users are concerned... No. The way that dependencies go from project to project is via artifacts installed/deployed into the local repository. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Creating a Custom Lifecycle
have you had a look at the unpackTypes configuration option of m-ear-p?
On 8 July 2010 16:28, asookazian asookaz...@gmail.com wrote:
Martin Höller wrote:
Am Mittwoch, 7. Juli 2010 18:46:34 schrieb asookazian:
There is some limited coverage of creating a custom lifecycle here:
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-cu
stom-lifecycle.html
but it also covers forking and parallel lifecycles, I'm not sure I'm
really
interested in that. I want to change the package lifecycle so that it
uses
war:explode goal rather than war:war goal.
What about just configuring the war:explode goal in your pom.xml? war:war
would still be executed, but is this a problem?
hth,
- martin
I just realized something very basic after reading first chapter of Maven
2:
Effective Implementation. The web application archive is produced in the
target directory, which is Maven's default working directory. There you
will find both the target/simple-webapp subdirectory that contains the
exploded, or unpacked, web application contents ready to be packaged, and
the target/simple-webapp.war file that contains those files after the
packaging process.
So perhaps if the unpack goal of the jboss-maven-plugin was modified to use
the already exploded WAR in the exploded EAR, then we would be good. At
least as far as JBoss users are concerned...
public void unpack( File zipFile, File targetDir )
throws IOException
{
FileInputStream in = new FileInputStream( zipFile );
ZipInputStream zipIn = new ZipInputStream( in );
File dir = targetDir.getCanonicalFile();
dir.mkdirs();
ZipEntry entry;
while ( ( entry = zipIn.getNextEntry() ) != null )
{
if ( entry.isDirectory() )
{
continue;
}
String file = targetDir + / + entry.getName();
new File( file ).getParentFile().getCanonicalFile().mkdirs();
FileOutputStream out = new FileOutputStream( file );
streamcopy( zipIn, out );
out.close();
}
zipIn.close();
}
http://svn.codehaus.org/mojo/tags/jboss-maven-plugin-1.4.1/src/main/java/org/codehaus/mojo/jboss/HardDeployMojo.java
--
View this message in context:
http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045103.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
Maven Plugins
Hi, Im a new user in maven. I have few doubts. 1. I have some BAT files that has to executed via maven 2. While executing my default commands.. I need to echo the status like Started first task 3. When the task gets failed user should get error message popup etc., 4. (a) Automatic repository update through maven (b) Maven calling ant to build .war (c) Copying the new created build file(.war) to local folder with date/time (d) Auto upload/deploy from build machine to server (e) Testing particular URLs/products to test the site flow (f) Sending mail regarding deployment status 5. Below is my example pom.xml, which im trying only (a) 4.0.0 com.test.example test 1.0-SNAPSHOT war mctest http://maven.apache.org UTF-8 junit junit 3.8.1 test org.codehaus.mojo exec-maven-plugin 1.1.1 exec D:\ D:\test.bat Thanks Paulwintech -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Plugins-tp1045208p1045208.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Maven Plugins
Why are you using Maven? I'm asking as it seems as you're trying to do everything NOT to use Maven's features... /Anders On Thu, Jul 8, 2010 at 21:17, Paulwintech paulwint...@gmail.com wrote: Hi, Im a new user in maven. I have few doubts. 1. I have some BAT files that has to executed via maven 2. While executing my default commands.. I need to echo the status like Started first task 3. When the task gets failed user should get error message popup etc., 4. (a) Automatic repository update through maven (b) Maven calling ant to build .war (c) Copying the new created build file(.war) to local folder with date/time (d) Auto upload/deploy from build machine to server (e) Testing particular URLs/products to test the site flow (f) Sending mail regarding deployment status 5. Below is my example pom.xml, which im trying only (a) 4.0.0 com.test.example test 1.0-SNAPSHOT war mctest http://maven.apache.org UTF-8 junit junit 3.8.1 test org.codehaus.mojo exec-maven-plugin 1.1.1 exec D:\ D:\test.bat Thanks Paulwintech -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Plugins-tp1045208p1045208.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Maven Plugins
Is there a question here? In general, it looks to me like you're trying to use Maven like Make or Ant which will only result in frustration. a, c, and d are intrinsic features of Maven - you don't need to do beyond some basic configuration b - the war plugin can do this e - failsafe can act as an integration test harness, although obviously you have to write the tests yourself f - most people have their CI server handle sending emails like this On 7/8/10 3:17 PM, Paulwintech wrote: Hi, Im a new user in maven. I have few doubts. 1. I have some BAT files that has to executed via maven 2. While executing my default commands.. I need to echo the status like Started first task 3. When the task gets failed user should get error message popup etc., 4. (a) Automatic repository update through maven (b) Maven calling ant to build .war (c) Copying the new created build file(.war) to local folder with date/time (d) Auto upload/deploy from build machine to server (e) Testing particular URLs/products to test the site flow (f) Sending mail regarding deployment status 5. Below is my example pom.xml, which im trying only (a) 4.0.0 com.test.example test 1.0-SNAPSHOT war mctest http://maven.apache.org UTF-8 junit junit 3.8.1 test org.codehaus.mojo exec-maven-plugin 1.1.1 exec D:\ D:\test.bat Thanks Paulwintech - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven APIs
Hi, Is it possible to re-use some some of the Maven APIs for repository management? For example, if I would like to implement code that saves content on the file system in group_id/artifact_id/version format. Is there a straight-forward path to reuse any Maven jars for that? (sorry if this should be in maven-developer, please let me know and I will cross-post). Regards, Rob
Re: Creating a Custom Lifecycle
stephenconnolly wrote: have you had a look at the unpackTypes configuration option of m-ear-p? That was exactly what I needed and it worked (I just did this in my profile): build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId version2.3.1/version configuration unpackTypeswar/unpackTypes /configuration /plugin /plugins /pluginManagement /build Thanks! Now I just need to write a simple Mojo/plugin that will copy the exploded EAR directory to the server/default/deploy directory in JBoss. cool. -- View this message in context: http://maven.40175.n5.nabble.com/Creating-a-Custom-Lifecycle-tp1044781p1045261.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 Plugins
You need to read some books, try to create, build and deploy a small Hello World web page using nothing but your IDE and Maven. Then take a good look at your development methodology and figure out where you are doing things s differently that the normal Maven life-cycle which works for everyone else does not work for you. Once you have got your head around the Maven life-cycle, take a good look at what you do now and think about how you can get Maven to automatically get you the result that you want without all the stuff that Ant forces you to do currently. BTW. Install Nexus as soon as you decide to go with Maven. I am still regretting the time we wasted struggling with dependencies before we installed Nexus. Make sure that your IDE has Maven embedded in it. I like STS (Eclipse from SpringSource) for that reason and others. If you do these simple things, you will be happy, productive and at peace with the universe. Ron On 08/07/2010 3:17 PM, Paulwintech wrote: Hi, Im a new user in maven. I have few doubts. 1. I have some BAT files that has to executed via maven 2. While executing my default commands.. I need to echo the status like Started first task 3. When the task gets failed user should get error message popup etc., 4. (a) Automatic repository update through maven (b) Maven calling ant to build .war (c) Copying the new created build file(.war) to local folder with date/time (d) Auto upload/deploy from build machine to server (e) Testing particular URLs/products to test the site flow (f) Sending mail regarding deployment status 5. Below is my example pom.xml, which im trying only (a) 4.0.0 com.test.example test 1.0-SNAPSHOT war mctest http://maven.apache.org UTF-8 junit junit 3.8.1 test org.codehaus.mojo exec-maven-plugin 1.1.1 exec D:\ D:\test.bat Thanks Paulwintech - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven jaxb2 plugin encoding issue
I set up jaxb2 plugin in my maven. It will generate code first then compile the code. My problem is that when jaxb2 generate the code, it will generate a commend line in the source code // Generated on: 2010 The time line include Chinese character for that I am using a Chinese version OS. When maven begins to build the source code, I will get an error that maven doesn't map UTF-8 character. How can I change the generated time character on jaxb2 plugin? thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-jaxb2-plugin-encoding-issue-tp1045281p1045281.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 jaxb2 plugin encoding issue
file an jira issue with sample maven project , and provide a fix if you can. jaxb2 plugin developer can work on it later. -D On Thu, Jul 8, 2010 at 7:36 PM, zhaoyi youhaod...@gmail.com wrote: I set up jaxb2 plugin in my maven. It will generate code first then compile the code. My problem is that when jaxb2 generate the code, it will generate a commend line in the source code // Generated on: 2010 The time line include Chinese character for that I am using a Chinese version OS. When maven begins to build the source code, I will get an error that maven doesn't map UTF-8 character. How can I change the generated time character on jaxb2 plugin? thanks. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-jaxb2-plugin-encoding-issue-tp1045281p1045281.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven jaxb2 plugin encoding issue
Does maven have a configuration for encoding or Calendar? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-jaxb2-plugin-encoding-issue-tp1045281p1045298.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
Processing Changes found in SCM
Hello, I'm running into an issue where a project that carries a very large number of static website files takes too long to deploy. Does anyone know of a mechanism in Maven that would allow me to check out through scm plugin only changed files? Personally I'm opposed to deploying only changed files but higher powers dictate this solution to me. I would rather use Maven than write a shell script to handle this special case. Thanks in advance, Dave
