Re: Assembly plugin
Neither worked.
${basedir} puts the directory where my pom is located, not the
baseDirectory in the zip file.
The outputDirectory tag did nothing. The zip file still only contained
myScript.bat
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
"Guillaume Polet"
To:
"Maven Users List"
Date:
07/12/2011 12:00 PM
Subject:
Re: Assembly plugin
1) Use ${basedir}
2) Use the outputDirectory tag (see
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html)
Cheers
Guillaume
Le 12/07/2011 17:54, Timothy Mcginnis a écrit :
> I have several questions about the assembly plugin and filtering with
the
> assembly plugin.
>
> 1) I would like to use the value in the assembly.xml
file
> in one of the filtered files but I can't seem to get it to work. I have
> tried several variations. I did put a ${project.version} in to make
sure
> filtering was working and this showed up as expected. I tried
> ${baseDirectory}
> ${assembly.baseDirectory}
> ${project.assembly.baseDirectory}
> ${project.baseDirectory}
> ${pom.baseDirectory}
> ${pom.assembly.baseDirectory}
>
> 2) I have a different assembly.xml where I only want to include one
script
> under a base directory. I want the zip file to contain the following:
> MyBaseDirectory/myScript.bat
>
> But all I get is a zip file with myScript.bat in it. Here is the
> assembly.xml file. The script myScript.bat resides in the directory
> batchscripts.
>
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
> http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
> http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
>
> batchscripts
>
> zip
>
> MyBaseDirectory
>
>
> batchscripts
> true
>
>
>
>
> Tim McGinnis
> 717 720-1962
> Web Development
> AES/PHEAA
>
==
> This message contains privileged and confidential information intended
for the above addressees only. If you
> receive this message in error please delete or destroy this message
and/or attachments.
>
> The sender of this message will fully cooperate in the civil and
criminal prosecution of any individual engaging
> in the unauthorized use of this message.
>
==
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Assembly plugin
I have several questions about the assembly plugin and filtering with the
assembly plugin.
1) I would like to use the value in the assembly.xml file
in one of the filtered files but I can't seem to get it to work. I have
tried several variations. I did put a ${project.version} in to make sure
filtering was working and this showed up as expected. I tried
${baseDirectory}
${assembly.baseDirectory}
${project.assembly.baseDirectory}
${project.baseDirectory}
${pom.baseDirectory}
${pom.assembly.baseDirectory}
2) I have a different assembly.xml where I only want to include one script
under a base directory. I want the zip file to contain the following:
MyBaseDirectory/myScript.bat
But all I get is a zip file with myScript.bat in it. Here is the
assembly.xml file. The script myScript.bat resides in the directory
batchscripts.
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
batchscripts
zip
MyBaseDirectory
batchscripts
true
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Re: Packaged jar cannot access class of a dependency??
Are you expecting this to run as part of the default packaging phase?
If so, I believe you are missing an section for the assembly
plugin that binds the 'single' goal to the packaging phase.
[...]
[...]
maven-assembly-plugin
2.2.1
jar-with-dependencies
make-assembly
package
single
[...]
See the "Execution: Building An Assembly" section of this page
http://maven.apache.org/plugins/maven-assembly-plugin/usage.html
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
Chris24300
To:
users@maven.apache.org
Date:
04/20/2011 08:25 AM
Subject:
Re: Packaged jar cannot access class of a dependency??
Thanks for replying with the link, I've already included the main class in
my
pom
Majority of my pom
Db4oServer
maven-compiler-plugin
1.5
1.5
org.apache.maven.plugins
maven-jar-plugin
${groupId}.TestClient
${groupId}
development
${pom.url}
maven-assembly-plugin
${groupId}.TestClient
jar-with-dependencies
--
View this message in context:
http://maven.40175.n5.nabble.com/Packaged-jar-cannot-access-class-of-a-dependency-tp4315587p4315651.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
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Re: maven ear plugin - simple example
You didn't specify the packaging type for the artifact.
ear
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
"Dave Levitt"
To:
"Maven Users List"
Date:
03/15/2011 10:56 AM
Subject:
maven ear plugin - simple example
I am having trouble using the ear plugin [version 2.5] with Maven
3.0.3, to create an EAR file for a simple stateless ejb.
I've tried the javaee 6 archetype from mojo - that seems to be just
for the ear module of a multi-module application - accordingly, I've
tried both single and multi module configurations but so far neither
has worked. I've tried following an example I've located at
http://agoncal.wordpress.com/2009/10/23/because-i-always-forget-how-to-use-maven-ear-plugin/
but I'm getting an empty ear file
I want to create a complete example that could be added to the usage
page for the plugin.
So, assuming that we want to package one java ee 6 Stateless Session
Bean [annotated @Stateless, one public method returning a fixed
String] like
package org.apache.maven.example;
import javax.ejb.Stateless;
@Stateless
public class Foo{
public String getTest(){
return "test";
}
}
And assuming that a multi module layout is used [parent, ejb module,
ear module] what should the pom for the ear module look like?
My [non working] example currently looks like
org.apache.example
jee6eartest
1.0-SNAPSHOT
fooEar
org.apache.example
fooejb
1.0-SNAPSHOT
ejb
org.apache.maven.plugins
maven.ear.plugin
2.5
6
groupId>org.apache.example
fooejb
When this is run, the ejb jar file is generate in its module, then
Maven builds the ear module.
The log shows
[WARNING] JAR will be empty - no content marked for inclusion!
[INFO] Building jar:
C:\work\jee6eartest\fooEar\target\fooEar-1.0-SNAPSHOT.jar
Does anyone have this working?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
.svn/tmp directory missing or corrupt
I am trying to release a project using release:perform. When it is
checking out the project from subversion I get the error
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
I run the svn cleanup and try again but still get the same error.
I can run the svn checkout from the command line and it works fine.
Here is the output
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Online Payment System
[INFO] OPS Core Model
[INFO] OPS Web Application
[INFO] OPS Enterprise Archiva.
[INFO]
[INFO] Building Online Payment System
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO]
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: svn --non-interactive checkout
svn+ssh://tmcgi...@leslie.aessuccess.org/svn/java/MavenPOC/tags/online-payment-system-1.74
checkout
[INFO] Working directory: C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT\target
[ERROR] The svn command failed.
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to checkout from SCM
Provider message:
The svn command failed.
Command output:
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 11 seconds
[INFO] Finished at: Fri Sep 03 08:36:27 EDT 2010
[INFO] Final Memory: 9M/27M
[INFO]
C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT>
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Re: release plugin rollback and subversion
Okay, thanks Brett. Now, can you take a look at my email in the Archiva list? Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Brett Porter" To: "Maven Users List" Date: 08/27/2010 10:55 AM Subject: Re: release plugin rollback and subversion Sent by: "Brett Porter" Yes, it's a known issue that rollback doesn't remove any created tags. You should remove it manually. - Brett On 27/08/2010, at 11:56 PM, Timothy Mcginnis wrote: > Hello, > > I am trying to use Subversion with Maven for the first time. For the past > two years I have been using CVS. > > My situation is that I run a "release:prepare" successfully. Then I need > to run a "release:rollback" to fix something. When I try to run the > "release:prepare" again I get an error saying the path already exists in > my subversion repository. And if I go check in there is definitely a tag > in subversion for the release. Do I have to manually tell subversion to > remove the tag? Or am I doing something wrong? > > Tim McGinnis > 717 720-1962 > Web Development > AES/PHEAA > == > This message contains privileged and confidential information intended for the above addressees only. If you > receive this message in error please delete or destroy this message and/or attachments. > > The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging > in the unauthorized use of this message. > == -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
release plugin rollback and subversion
Hello, I am trying to use Subversion with Maven for the first time. For the past two years I have been using CVS. My situation is that I run a "release:prepare" successfully. Then I need to run a "release:rollback" to fix something. When I try to run the "release:prepare" again I get an error saying the path already exists in my subversion repository. And if I go check in there is definitely a tag in subversion for the release. Do I have to manually tell subversion to remove the tag? Or am I doing something wrong? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Ear plugin issue
In add
${project.artifactId}-${project.version}.jar
and make sure your project in Eclipse is named using the
[artifactId]-[version] Name Template.
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
nishant@hsbcib.com
To:
"Maven Users List"
Cc:
users@maven.apache.org
Date:
08/26/2010 10:21 AM
Subject:
Re: Ear plugin issue
It seems the attachments are not allowed. I have included the ear pom
below..
**
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
ProjectX
root
1.0
root.ProjectX
EarAssembler
1.0
EarAssembler
ear
org.apache.maven.plugins
maven-ear-plugin
2.4.2
root.ProjectX
ClientModules
true
root.ProjectX
ClientModules
1.0
**
Thanks
Nishant RAJ/HBEU/h...@hsbc
Aug 26 2010 15:17
Mail Size: 8020
Please respond to
"Maven Users List"
To
users@maven.apache.org
cc
Subject
Ear plugin issue
Entity
HSBC Bank plc - HBEU
Hi All,
I am trying to get the ear plugin working.
Followed all the guidelines but could not get it working as its not able
to "find" the module that I want to package within the ear
It looks for the module in my nexus repository but does not find it.
I have also got the "Resolve workspace project dependencies" enables in
eclipse.
Pom is attached.
Please advice as I have been struggling with the same for few hrs now.
Thanks
Nishant
HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority
- SAVE PAPER - THINK BEFORE YOU
PRINT! This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page attached
hereto must be read in conjunction with any disclaimer which forms part of
it. Unless otherwise stated, this transmission is neither an offer nor the
solicitation of an offer to sell or purchase any investment. Its contents
are based on information obtained from sources believed to be reliable but
HSBC makes no representation and accepts no responsibility or liability as
to its completeness or accuracy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
HSBC Bank plc
Registered Office: 8 Canada Square, London E14 5HQ
Registered in England - Number 14259
Authorised and regulated by the Financial Services Authority
-
SAVE PAPER - THINK BEFORE YOU PRINT!
This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and/or distributed to any other person. Each page
attached hereto must be read in conjunction with any disclaimer
which forms part of it. Unless otherwise stated, this transmission
is neither an offer nor the solicitation of an offer to sell or
purchase any investment. Its contents are based on information
obtained from sources believed to be reliable but HSBC makes no
representation and accepts no responsibility or liability as to its
completeness or accuracy.
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Re: Using Subversion and Maven
I mis-spoke when I said "it just used the client in Eclipse". I think cvs uses a client packaged with one of the maven-scm-provider-cvs-??? jars. Although I have not looked into the source code to verify this. I just assumed the subversion provider would do the same. Seems like it doesn't due to a licensing issue from what someone else said. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Nicola Musatti" To: "Maven Users List" Date: 08/25/2010 05:04 AM Subject: Re: Using Subversion and Maven Did you install an Eclipse Subversion plugin, such as Subversive or Subclipse? This doesn't seem to have much to do with Maven... Cheers, Nicola Musatti Timothy Mcginnis wrote: > Well, I probably should have posted this in the M2Eclipse list (which I > have done since then). Previously when using cvs it just used the client > in Eclipse, but when I tried to do the same with subversion it gave me > this error. > > Tim McGinnis > 717 720-1962 > Web Development > AES/PHEAA > > > > From: > "Wayne Fay" > To: > "Maven Users List" > Date: > 08/24/2010 03:04 PM > Subject: > Re: Using Subversion and Maven > > > > >> with Subversion. I am getting the error "'svn' is not recognized as an >> internal or external command". From what I can find on google I >> > actually > >> need to have svn installed separately from Maven. Is this correct? >> > Yes. > > What causes you to assume anything else? Is there some documentation > that should be updated or fixed? I've seen this question multiple > times on this list. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > == > This message contains privileged and confidential information intended for the above addressees only. If you > receive this message in error please delete or destroy this message and/or attachments. > > The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging > in the unauthorized use of this message. > == > > Chi riceve il presente messaggio e' tenuto a verificare se lo stesso non gli sia pervenuto per errore. In tal caso e' pregato di avvisare immediatamente il mittente e, tenuto conto delle responsabilita' connesse all'indebito utilizzo e/o divulgazione del messaggio e/o delle informazioni in esso contenute, voglia cancellare l'originale e distruggere le varie copie o stampe. The receiver of this message is required to check if he/she has received it erroneously. If so, the receiver is requested to immediately inform the sender and - in consideration of the responsibilities arising from undue use and/or disclosure of the message and/or the information contained therein - destroy the original message and any copy or printout thereof. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Using Subversion and Maven
Well, I probably should have posted this in the M2Eclipse list (which I have done since then). Previously when using cvs it just used the client in Eclipse, but when I tried to do the same with subversion it gave me this error. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Wayne Fay" To: "Maven Users List" Date: 08/24/2010 03:04 PM Subject: Re: Using Subversion and Maven > with Subversion. I am getting the error "'svn' is not recognized as an > internal or external command". From what I can find on google I actually > need to have svn installed separately from Maven. Is this correct? Yes. What causes you to assume anything else? Is there some documentation that should be updated or fixed? I've seen this question multiple times on this list. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Using Subversion and Maven
I am moving our dev team from CVS to Subversion and started testing Maven with Subversion. I am getting the error "'svn' is not recognized as an internal or external command". From what I can find on google I actually need to have svn installed separately from Maven. Is this correct? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
javadoc does not work in release
I am using Maven 2.2.1 and release plugin 2.0-beta-7. I had the maven-javadoc-plugin 2.6 configured in my tag. I have a project that has three sub-modules; core, war, ear. When I run the release:perform it bails out on the war saying it can't resolve the core artifact. I went through a LOT of changes and finally found that if I move the maven-javadoc-plugin version back to 2.2 it works fine. Is anything above version 2.2 in maven-javadoc-plugin incompatible with 2.2.1? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Confused about compiler used for release
That was it. My path and java_home were pointing to a 1.5 jre. I fixed that and it works perfectly. Thank you! Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Stephen Connolly" To: "Maven Users List" Date: 07/23/2010 02:00 AM Subject: Re: Confused about compiler used for release probably you have a disconnect between your PATH and JAVA_HOME environment variables. release:prepare sort of forks a maven process and the environment may be different in that case. For example we have a project that is half built with ANT and half built with Maven. currently our release process is mvn release:prepare release:perform cd target/checkout ant deploy but yet, if we bind antrun:run or exec:exec to the deploy phase and try and do an ant deploy there it fails due to some subtle environment variable differences in the forked maven... strangely mvn deploy works just fine at calling ant deploy, but when in the release:perform the ant script bombs out! -Stephen PS ignore Martin the robot's reply, it's completely irrelevant On 22 July 2010 19:01, Timothy Mcginnis wrote: > I am confused about something. > > I have a project where I have specified that the compiler target and > source are to be 1.6. I can run mvn deploy and everything works fine. > When I try to run mvn release:prepare it tells me the compiler (javac) > does not support 1.6. Why is it using two different compilers?? > > Tim McGinnis > 717 720-1962 > Web Development > AES/PHEAA > > == > This message contains privileged and confidential information intended for > the above addressees only. If you > receive this message in error please delete or destroy this message and/or > attachments. > > The sender of this message will fully cooperate in the civil and criminal > prosecution of any individual engaging > in the unauthorized use of this message. > > == > == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Confused about compiler used for release
I am confused about something. I have a project where I have specified that the compiler target and source are to be 1.6. I can run mvn deploy and everything works fine. When I try to run mvn release:prepare it tells me the compiler (javac) does not support 1.6. Why is it using two different compilers?? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Eclipse Maven WAS
Yes. We use M2Eclipse (9.8 I know its old) and just configure the poms
normally.
In RSA make a few preference changes.
Java EE -
in the Classpath containers box uncheck Use Ear Libraries
classpath container
Java EE->Project ---
uncheck Add project to an EAR
under Dynamic Web Project set the following fields
Default Source Folder: src/main/java
Output Folder: /src/main/webapp/WEB-INF/classes
Content Directory: /src/main/webapp
Make sure your build tags are set up correctly.
Here is a war build tag
src/main/webapp/WEB-INF/classes
org.apache.maven.plugins
maven-war-plugin
2.1-beta-1
aesaa-web
WEB-INF/lib
/*.jar
src/main/
webapp/META-INF/MANIFEST.MF
${project.groupId}
${project.artifactId}
${project.version}
Here is a ejb build tag
org.apache.maven.plugins
maven-ejb-plugin
2.2
3.0
src
/main/resources/META-INF/MANIFEST.MF
${project.groupId}
${project.artifactId}
${project.version}
Here is a ear build tag
org.apache.maven.plugins
maven-ear-plugin
5
true
B2B Auth Service
com.aes
.common.authentication-authorization
aesaa-
ejb
aesaa-ejb-${version}.jar
com.aes
.common.authentication-authorization
aesaa-
http-router-war
aesaa-http-router-war-${version}.war
/B2BAuthService
src
/main/application/META-INF/MANIFEST.MF
${project.groupId}
${project.artifactId}
${project.version}
And finally when importing the project make sure to open the Advanced tab
on the Maven Projects wizard and select the Name template:
[artifactId]-[version].
Everything should hot deploy and using run configs you should be able to
build your artifacts from right inside RSA.
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
"Refr Bruhl"
To:
users@maven.apache.org
Date:
07/22/2010 10:27 AM
Subject:
Eclipse Maven WAS
Team
This is probably a newbie question.
We're trying to integrate maven with eclipse and websphere.
The goal is to use "class reloading" in our development environment to
allow for
rapid developtment.
Has anyone else done this and gotten it to work? If so what steps did you
use?
T
Problem with ReleaseDescriptor model
I have been trying to compile the 2.0 release plugin and I am having a
problem with building the ReleaseDescriptor class from the model.
It seems to build a class but there are parts missing. I have errors like
ReleaseDescriptor.ORIGINAL_VERSION cannot be resolved
ReleaseDescriptor.RELEASE_KEY cannot be resolved
ReleaseDescriptor.DEVELOPMENT_KEY cannot be resolved
I looked at the class in target/generated-sources/modello and all I have
is the following.
/*
=== DO NOT EDIT THIS FILE
Generated by Modello 1.1 on 2010-06-25 09:18:32,
any modifications will be overwritten.
==
*/
package org.apache.maven.shared.release.config;
/**
* Class ReleaseDescriptor.
*
* @version $Revision$ $Date$
*/
public class ReleaseDescriptor
implements java.io.Serializable
{
//--/
//- Class/Member Variables -/
//--/
/**
* Field modelEncoding.
*/
private String modelEncoding = "UTF-8";
//---/
//- Methods -/
//---/
/**
* Get the modelEncoding field.
*
* @return String
*/
public String getModelEncoding()
{
return this.modelEncoding;
} //-- String getModelEncoding()
/**
* Set the modelEncoding field.
*
* @param modelEncoding
*/
public void setModelEncoding( String modelEncoding )
{
this.modelEncoding = modelEncoding;
} //-- void setModelEncoding( String )
}
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
generateApplicationXml and release plugin
I have the tag set to true for my maven-ear-plugin. But this seems to cause a problem when I run release:prepare. The application.xml file gets modified during the prepare (which is good because it sets the right version numbers on the uri) but then the application.xml is committed to my SCM and release:prepare stops because of this. Is there a way to use generateApplicationXml with release? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
SCM for cvs version 1.12.12
I am using CVS for my SCM. I have one repository that is version 1.11.14 and one that is 1.12.12. When I try to do a release using the 1.12.12 CVS repository I get the error "Received unknown response from server". But when I use the 1.11.14 repository it works. Is there a CVS plugin that will work with 1.12.12? And how do I configure my pom to use it? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Preventing an inherited report from running
The skip helps. But there is one I'd like to get rid of, the Cobertura report. And it doesn't have a skip. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Wendy Smoak" To: "Maven Users List" Date: 05/20/2010 04:33 PM Subject: Re: Preventing an inherited report from running On Thu, May 20, 2010 at 4:25 PM, Timothy Mcginnis wrote: > I have a master pom that specifies the reports to be run. In one of the > child projects I do not want to run one of those reports. How do I > prevent it from running? In general you can't un-inherit things, but some plugins have a "skip" parameter that you can configure. If that doesn't help, let us know what report it is and how it's configured... -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Preventing an inherited report from running
I have a master pom that specifies the reports to be run. In one of the child projects I do not want to run one of those reports. How do I prevent it from running? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
release:prepare - EMBEDDED/bin/mvn.bat not found
I am attempting to run a release:prepare using M2Eclipse. At first I
thought my issue was a M2Eclipse issue so I posted on that list but did
not get much of a response. After looking at it a while it seems it might
be a issue with the release plugin, or at least someone familiar with the
release plugin my be able to point me in the right direction.
When I run a release:prepare I get the error "Maven executable not found
at: C:\Documents and
Settings\tmcginni\rational\workspace\aes-maven-master-1.4.16-SNAPSHOT\EMBEDDED\bin\mvn.bat
".
Why is it looking for "mvn.bat"? Here is a snippet of the debug output.
[INFO] Building AES Maven Master 1.4.16
[INFO]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: com.aes:aes-maven-master:1.4.16
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [test]
[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare
(default-cli)
[DEBUG] Style: Aggregating
[DEBUG] Configuration:
${addSchema}
${allowReleasePluginSnapshot}
${ignoreSnapshots}
${arguments}
true
${basedir}
${commitByProject}
${developmentVersion}
${dryRun}
${generateReleasePoms}
${mavenExecutorId}
${password}
${pomFileName}
${preparationGoals}
${project}
${reactorProjects}
${releaseVersion}
${remoteTagging}
${resume}
${scmCommentPrefix}
${settings}
${tag}
${tagBase}
${updateDependencies}
${useEditMode}
${username}
[DEBUG]
===
[INFO]
[INFO] --- maven-release-plugin:2.0-beta-9:prepare (default-cli) @
aes-maven-master ---
[DEBUG] Created new class realm
plugin>org.apache.maven.plugins:maven-release-plugin:2.0-beta-9
[DEBUG] Populating class realm
plugin>org.apache.maven.plugins:maven-release-plugin:2.0-beta-9
[DEBUG] Included:
org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-9
[DEBUG] Included:
org.apache.maven.release:maven-release-manager:jar:2.0-beta-9
[DEBUG] Included: junit:junit:jar:3.8.1
[DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.5.6
[DEBUG] Included:
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-6
[DEBUG] Included: org.apache.maven.shared:maven-invoker:jar:2.0.9
[DEBUG] Included: commons-cli:commons-cli:jar:1.0
[DEBUG] Included: commons-logging:commons-logging:jar:1.0
[DEBUG] Included: commons-lang:commons-lang:jar:1.0
[DEBUG] Included:
org.apache.maven.scm:maven-scm-providers-standard:pom:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-accurev:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-api:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.2
[DEBUG] Included: regexp:regexp:jar:1.3
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-cvsexe:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-cvs-commons:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-cvsjava:jar:1.2
[DEBUG] Included: org.netbeans.lib:cvsclient:jar:20060125
[DEBUG] Included: ch.ethz.ganymed:ganymed-ssh2:jar:build210
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-gitexe:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-git-commons:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-hg:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-perforce:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-starteam:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-svnexe:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-svn-commons:jar:1.2
[DEBUG] Included:
org.apache.maven.scm:maven-scm-provider-synergy:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-provider-vss:jar:1.2
[DEBUG] Included: org.apache.maven.scm:maven-scm-manager-plexus:jar:1.2
[DEBUG] Included: jdom:jdom:jar:1.0
[DEBUG] Included: jaxen:jaxen:jar:1.1-beta-8
[DEBUG] Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG] Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG] Excluded: classworlds:classworlds:jar:1.1-alpha-2
[DEBUG] Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.0.8
[DEBUG] Excluded:
org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2
[DEBUG] Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG] Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.8
[DEBUG] Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG] Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG] Excluded:
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9
[DEBUG] Excluded: org.apa
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
org.apache.maven.plugins
maven-dependency-plugin
2.1
false
unpack-javascripts
unpack
package
${project.build.directory}/war/scripts
still no effect, even though the maven-dependency-plugin is now mentioned
twice in the WAR's POM.. hmm, do I have to do the same in the parent POM?
i.e. specify the plugin in the build's plugin management?
\
On Thu, May 13, 2010 at 1:08 PM, Timothy Mcginnis
wrote:
> Are you defining the plugin in your WAR POM also? Using the
> pluginManagement I believe you also need to call out the use of the
plugin
> in the WAR POM, but don't define any of the execution/configuration
data,
> that is provided by the pluginManagement in the profile.
>
>
> Profile provides this:
>
>
>
> ...
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
> true
>
>
> unpack-javascripts
>
> unpack
>
> package
>
>
${project.build.directory}/war/scripts
>
>
>
>
>
>
>
> WAR POM specifies this:
>
>
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
>
>
>
>
> Tim McGinnis
> 717 720-1962
> Web Development
> AES/PHEAA
>
>
>
> From:
> "Shan Syed"
> To:
> "Maven Users List"
> Date:
> 05/13/2010 12:51 PM
> Subject:
> Re: inheriting and reusing the same plugin for different purposes?
doesn't
> seem to find the right executions
>
>
>
> thanks - how would I set this up?
> I tried to specify two profiles in my parent POM, each with their own
> pluginManagement blocks, containing a maven-dependency-plugin
> configuration,
> and then activated the profile in the WAR projects' POMs, but there is
no
> result
>
> I basically want my plugins' meta config stored in the root, and
specific
> configs applied in the WAR projects
>
>
>
> On Thu, May 13, 2010 at 10:26 AM, Timothy Mcginnis
> wrote:
>
> > What about using profiles? Define 3 profiles; one for wsdl only, one
> for
> > javascript only, and one for both. Then have the war project activate
> the
> > one it needs.
> >
> > Tim McGinnis
> > 717 720-1962
> > Web Development
> > AES/PHEAA
> >
> >
> >
> > From:
> > "Shan Syed"
> > To:
> > "Maven Users List" , kalpa...@gmail.com
> > Date:
> > 05/13/2010 09:54 AM
> > Subject:
> > Re: inheriting and reusing the same plugin for different purposes?
> doesn't
> > seem to find the right executions
> >
> >
> >
> > Thanks, but the problem is that when I do that, both executions occur,
> > even
> > when I specify inheritance=false.
> >
> > I basically need to use the same plugin for two different purposes,
> > without
> > either of them affecting the other; I tried to specify different
> versions
> > for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for
the
> > other), but no dice.
> >
> > Running mvn help:effective-pom on my WAR projects always shows the
> second
> > maven-dependency-plugin configuration from the root POM in the
> > pluginManagement section
> > BUT
> > in the actual plugin block, it shows the following (below)
> > (note the second execution, with not configuration or anything
> associated
> > with it)
> >
> > What is the exact logic for the merging of plugin configs in a
> multimodule
> > project?
> >
> > thanks
> >
> > S
> >
> >
> > maven-dependency-plugin
> > 2.1
> >
> >
> > unpack-wsdls
> > generate-resources
> >
> > unpack
> >
> >
> >
> >
> >
>
>
C:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl
> >
> >
> >
> > unpack-javascripts
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
Are you defining the plugin in your WAR POM also? Using the
pluginManagement I believe you also need to call out the use of the plugin
in the WAR POM, but don't define any of the execution/configuration data,
that is provided by the pluginManagement in the profile.
Profile provides this:
...
org.apache.maven.plugins
maven-dependency-plugin
true
unpack-javascripts
unpack
package
${project.build.directory}/war/scripts
WAR POM specifies this:
org.apache.maven.plugins
maven-dependency-plugin
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
"Shan Syed"
To:
"Maven Users List"
Date:
05/13/2010 12:51 PM
Subject:
Re: inheriting and reusing the same plugin for different purposes? doesn't
seem to find the right executions
thanks - how would I set this up?
I tried to specify two profiles in my parent POM, each with their own
pluginManagement blocks, containing a maven-dependency-plugin
configuration,
and then activated the profile in the WAR projects' POMs, but there is no
result
I basically want my plugins' meta config stored in the root, and specific
configs applied in the WAR projects
On Thu, May 13, 2010 at 10:26 AM, Timothy Mcginnis
wrote:
> What about using profiles? Define 3 profiles; one for wsdl only, one
for
> javascript only, and one for both. Then have the war project activate
the
> one it needs.
>
> Tim McGinnis
> 717 720-1962
> Web Development
> AES/PHEAA
>
>
>
> From:
> "Shan Syed"
> To:
> "Maven Users List" , kalpa...@gmail.com
> Date:
> 05/13/2010 09:54 AM
> Subject:
> Re: inheriting and reusing the same plugin for different purposes?
doesn't
> seem to find the right executions
>
>
>
> Thanks, but the problem is that when I do that, both executions occur,
> even
> when I specify inheritance=false.
>
> I basically need to use the same plugin for two different purposes,
> without
> either of them affecting the other; I tried to specify different
versions
> for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for the
> other), but no dice.
>
> Running mvn help:effective-pom on my WAR projects always shows the
second
> maven-dependency-plugin configuration from the root POM in the
> pluginManagement section
> BUT
> in the actual plugin block, it shows the following (below)
> (note the second execution, with not configuration or anything
associated
> with it)
>
> What is the exact logic for the merging of plugin configs in a
multimodule
> project?
>
> thanks
>
> S
>
>
> maven-dependency-plugin
> 2.1
>
>
> unpack-wsdls
> generate-resources
>
> unpack
>
>
>
>
>
C:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl
>
>
>
> unpack-javascripts
>
>
>
>
>
> sk-javascript-token
> com.securekey.javascript
> 1.0-SNAPSHOT
> javascript
> zip
>
>
>
>
>
> On Thu, May 13, 2010 at 4:54 AM, Kalpak Gadre
wrote:
>
> > I have never tried declaring the same plugin twice, but you can simply
> > define more executions in the same plugin declaration like,
> >
> >
> >
> > one
> > .
> > .
> >
> >
> > two
> > .
> > .
> >
> >
> >
> >
> > Thanks,
> >
> > Kalpak
> >
> >
> > Here's my scenario: I have a large multimodule project whose WARs
share
> >> certain dependencies, which are packaged as zips by a few simple
> >> assemblies
> >> I wrote.
> >>
> >> I am using the maven-dependency-plugin to unpack the contents of
these
> >> zips
> >> into their destination folders in the webapps.
> >>
> >> However, to reduce clutter and minimize maintenance, the majority of
> the
> >> plugin configuration is in the root POM, like so:
> >> (note that I am using the same plugin twice for two different reasons
-
> is
> >> this valid?)
> >>
> >>
> >>
> >>
> >> ...
> >>
> >>
> >> org.apache.maven.plugins
> >> maven-dependency-plugin
> >> true
> >>
>
Re: inheriting and reusing the same plugin for different purposes? doesn't seem to find the right executions
What about using profiles? Define 3 profiles; one for wsdl only, one for
javascript only, and one for both. Then have the war project activate the
one it needs.
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
From:
"Shan Syed"
To:
"Maven Users List" , kalpa...@gmail.com
Date:
05/13/2010 09:54 AM
Subject:
Re: inheriting and reusing the same plugin for different purposes? doesn't
seem to find the right executions
Thanks, but the problem is that when I do that, both executions occur,
even
when I specify inheritance=false.
I basically need to use the same plugin for two different purposes,
without
either of them affecting the other; I tried to specify different versions
for the mvn dep plugin (i.e. in one block, specify 2.0, and 2.1 for the
other), but no dice.
Running mvn help:effective-pom on my WAR projects always shows the second
maven-dependency-plugin configuration from the root POM in the
pluginManagement section
BUT
in the actual plugin block, it shows the following (below)
(note the second execution, with not configuration or anything associated
with it)
What is the exact logic for the merging of plugin configs in a multimodule
project?
thanks
S
maven-dependency-plugin
2.1
unpack-wsdls
generate-resources
unpack
C:\dev\sk\sk-saml\sk-saml-web\sk-saml-server\target/war/WEB-INF/wsdl
unpack-javascripts
sk-javascript-token
com.securekey.javascript
1.0-SNAPSHOT
javascript
zip
On Thu, May 13, 2010 at 4:54 AM, Kalpak Gadre wrote:
> I have never tried declaring the same plugin twice, but you can simply
> define more executions in the same plugin declaration like,
>
>
>
> one
> .
> .
>
>
> two
> .
> .
>
>
>
>
> Thanks,
>
> Kalpak
>
>
> Here's my scenario: I have a large multimodule project whose WARs share
>> certain dependencies, which are packaged as zips by a few simple
>> assemblies
>> I wrote.
>>
>> I am using the maven-dependency-plugin to unpack the contents of these
>> zips
>> into their destination folders in the webapps.
>>
>> However, to reduce clutter and minimize maintenance, the majority of
the
>> plugin configuration is in the root POM, like so:
>> (note that I am using the same plugin twice for two different reasons -
is
>> this valid?)
>>
>>
>>
>>
>> ...
>>
>>
>> org.apache.maven.plugins
>> maven-dependency-plugin
>> true
>>
>>
>>unpack-javascripts
>>
>> unpack
>>
>>package
>>
>>
>>
${project.build.directory}/war/scripts
>>
>>
>>
>>
>>
>>
>> org.apache.maven.plugins
>> maven-dependency-plugin
>> true
>>
>>
>>unpack-wsdls
>>
>> unpack
>>
>>generate-resources
>>
>>
>>
>>
${project.build.directory}/war/WEB-INF/wsdl
>>
>>
>>
>>
>>
>>
>>
>>
>> Some WARs need the WSDLs, some need the javascript files, while others
>> don't
>> need either - it will be up to the developers creating those projects.
>>
>> Here is an example usage in one of the WARs (note the ID of the
execution,
>> which is expected to be used to merge the whole configuration)
>>
>>
>>
>>
>> maven-dependency-plugin
>> org.apache.maven.plugins
>> true
>>
>>
>> unpack-javascripts
>>
>>
>>
>>
>>
>>
>> sk-javascript-token
>>
>> com.securekey.javascript
>> ${project.version}
>>javascript
>>zip
>>
>>
>>
>>
>>
>>
>>
>> So in general, the plugin configuration in the root POM will enforce
som
Re: Why define repositories in settings.xml and pom?
Sorry about that secure post. I hit the wrong button. Thanks for all your discussion. I now understand why repositories must be defined in the pom. Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Justin Edelson" To: "Maven Users List" Date: 05/03/2010 10:20 PM Subject: Re: Why define repositories in settings.xml and pom? This seems like a very specific use case. I think it's more to the point to say that many people (including, I suspect, 100% of Maven developers) use the same workstation to work on projects which are deployed to different repositories, e.g. apache, codehaus, java.net, a corporate repository, etc. It doesn't make sense to deploy an apache.org project to the codehaus repository or vice versa. Nor do you want to deploy corporate artifacts to the java.net repository. Thus, artifact deployment/distribution is project-specific. However, in all of those cases, you can use the same mirror of central. And which mirror you pick should be based on your environment, not the particular project. It should either be the closet mirror or a "nearby" caching repository manager. If you want build reproducibility, you should be using release artifacts and only reference repositories with immutability rules. You should be able to reproduce a build using an entirely different mirror (again, assuming repository immutability). If you reference mutable repositories, you lose build reproducibility regardless of what you put in your pom or settings.xml. Justin On 5/3/10 11:59 AM, Thiessen, Todd (Todd) wrote: >> I think the best way to think about this is that the read >> side is (or should >> be) an aspect of your environment whereas the write side is >> an aspect of your project. > > Very true. But we should make it clear why reading is an aspect of your environment whereas writing is an aspect of your project. > > I think the reason is when your deploying a project, you are doing so because you are making an actual change to the code itself. If you are already changing the code and the server to which you deploy to also happens to change, it is a relatively simple matter to change the pom at the same time you are changing the code. > > However, you may want to build an EXACT version of software that was previously deployed but the repos you read from may not be the same since the time the software was first deployed to the time you want to repeat the build. Thus you don't want to touch any of the source code, including the pom. You can change the settings.xml file point to the repos you are currently reading from. > - > 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 == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Why define repositories in settings.xml and pom?
I am a confused about where repositories need to be defined. I have my repositories defined in my settings.xml file under my default profile. default_profile true archiva.internal Internal Release Repository http://2e02057b.aessuccess.org:8085/archiva/repository/internal/ false true archiva.snapshots Internal Snapshot Repository http://2e02057b.aessuccess.org:8085/archiva/repository/snapshots/ true false I thought this would tell Maven where to store and retrieve all my artifacts. But when I run a deploy it gives me the error Deployment failed: repository element was not specified in the pom inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter If I define the repositories in the pom using the distributionManagement element it works fine. But this seems confusing to me. Why do I have to define them in both places? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
finalName in Ear plugin
What is the purpose of the tag in the Ear plugin? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: Site plugin overwrites index.apt
Although I can't use 2.1 because I am stuck using m2eclipse .98 at the moment, the project-info-reports information helped me resolve the problem. Thanks, Tim McGinnis 717 720-1962 Web Development AES/PHEAA From: "Kathryn Huxtable" To: "Maven Users List" Date: 04/08/2010 11:33 AM Subject: Re: Site plugin overwrites index.apt Try version 2.1. I generally specify the reports I want in the project-info-reports plugin and don't specify the "about" report. -K On Apr 8, 2010, at 10:28 AM, Timothy Mcginnis wrote: > I have a site for my project that defines a index.apt file. When I run > the mvn site:site (or any other site goal) my index.apt file is ignored > and a index.html file is created with just the description from my pom. > This was working before where I would get the index.html file that I > provided. But something has changed and I am not sure what is causing > this different behavior. > > I am using version 2.0.1 of the site plugin. > > Thanks, > > Tim McGinnis > 717 720-1962 > Web Development > AES/PHEAA > == > This message contains privileged and confidential information intended for the above addressees only. If you > receive this message in error please delete or destroy this message and/or attachments. > > The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging > in the unauthorized use of this message. > == - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Site plugin overwrites index.apt
I have a site for my project that defines a index.apt file. When I run the mvn site:site (or any other site goal) my index.apt file is ignored and a index.html file is created with just the description from my pom. This was working before where I would get the index.html file that I provided. But something has changed and I am not sure what is causing this different behavior. I am using version 2.0.1 of the site plugin. Thanks, Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
