Re: Embedded error: Prohibited package name: java.lang
Hi John-
so plugin.xml would contain something like
outputDirectory
java.lang.String
true
true
The directory for the generated mar.
marName
java.lang.String
true
true
The name of the generated mar.
classifier
java.lang.String
false
true
Classifier to add to the artifact generated. If
given, the artifact will be an attachment instead.
groupId
java.lang.String
true
true
The plugin's groupId.
artifactId
java.lang.String
true
true
The plugin's artifactId.
version
java.lang.String
false
true
The plugin's version.
goal
java.lang.String
true
true
The mojo's goal that we're looking for, as an extra
validation step.
implementation="java.lang.String">${project.build.finalName}
implementation="java.lang.String">${project.build.directory}
${groupId}
implementation="java.lang.String">${artifactId}
${version}
${goal}
Anyone else?
Martin
- Original Message -
From: "John" <[EMAIL PROTECTED]>
To: "Maven Users List"
Sent: Saturday, May 31, 2008 6:49 PM
Subject: Embedded error: Prohibited package name: java.lang
I am trying to use Maven 2.0.9 on OS X, with the latest Apple updates, and
am getting the following error when I run a basic "mvn install site"
command:
[INFO] Compiling 1 source file to
/Users/john/downloads/jms-mdb-sample/jms-mdb-sample-ejb/target/classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Fatal error compiling
Embedded error: Prohibited package name: java.lang
I have tried to research the error by doing some googling but haven't come
up with any helpful information.
I would be very appreciative of any assistance to help me get past this.
Thanks,
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Embedded error: Prohibited package name: java.lang
I am trying to use Maven 2.0.9 on OS X, with the latest Apple updates, and am getting the following error when I run a basic "mvn install site" command: [INFO] Compiling 1 source file to /Users/john/downloads/jms-mdb-sample/jms-mdb-sample-ejb/target/classes [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Fatal error compiling Embedded error: Prohibited package name: java.lang I have tried to research the error by doing some googling but haven't come up with any helpful information. I would be very appreciative of any assistance to help me get past this. Thanks, John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: selecting profile in the pom.xml file
Hi Simon in your settings.xml define your then activate the predefined profile by placing the profile in e.g. freeform-lutece lutece:exploded,lutece:inplace,lutece:assembly,lutece:site-assembly webapp ... freeform-lutece http://dev.lutece.paris.fr/wikilutece/index.php?title=The_plugin_maven2_%22netbeans-freeform%22Bon Chance,Martin- Original Message - From: "simon" <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Saturday, May 31, 2008 12:32 PM Subject: Re: selecting profile in the pom.xml file On Sat, 2008-05-31 at 18:20 +0200, Stefano Nichele wrote: Hi Mick, thanks for your comment, but maybe my question was not clear enough. It seems that in the settings.xml, you comment the profile that you don't want to use according to the project that you are building. My requirement is a bit different. In my settings.xml I have profileA and profileB. ProfileA is the active one. Now I would like that project1 uses profileA and project2 uses profileB but I don't want to change my settings.xml anytime. I need something to say in the pom file of the project2 that the profile to use is profileB. For profiles declared within a pom, I believe that the values defined in the pom can be used in the activation section of the profile. But I don't know of any way for a pom to select a profile from an external settings file. The properties defined in a pom cannot be referenced from an external profile definition. Note that in general, stuff in settings.xml (including profiles) should be used as little as possible, as it makes builds unrepeatable (it controls the build, but is not under version control). If you can move your profile from settings.xml into the pom that would be the best solution.. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: selecting profile in the pom.xml file
On Sat, 2008-05-31 at 18:20 +0200, Stefano Nichele wrote: > Hi Mick, > thanks for your comment, but maybe my question was not clear enough. It > seems that in the settings.xml, you comment the profile that you don't > want to use according to the project that you are building. My > requirement is a bit different. > In my settings.xml I have profileA and profileB. ProfileA is the active one. > > Now I would like that project1 uses profileA and project2 uses profileB > but I don't want to change my settings.xml anytime. I need something to > say in the pom file of the project2 that the profile to use is profileB. For profiles declared within a pom, I believe that the values defined in the pom can be used in the activation section of the profile. But I don't know of any way for a pom to select a profile from an external settings file. The properties defined in a pom cannot be referenced from an external profile definition. Note that in general, stuff in settings.xml (including profiles) should be used as little as possible, as it makes builds unrepeatable (it controls the build, but is not under version control). If you can move your profile from settings.xml into the pom that would be the best solution.. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: selecting profile in the pom.xml file
Hi Mick, thanks for your comment, but maybe my question was not clear enough. It seems that in the settings.xml, you comment the profile that you don't want to use according to the project that you are building. My requirement is a bit different. In my settings.xml I have profileA and profileB. ProfileA is the active one. Now I would like that project1 uses profileA and project2 uses profileB but I don't want to change my settings.xml anytime. I need something to say in the pom file of the project2 that the profile to use is profileB. Ste Mick Knutson wrote: Yes. I add this at the bottom of my settings.xml: local-baselogic tomcat5.5 On Sat, May 31, 2008 at 7:48 AM, Stefano Nichele <[EMAIL PROTECTED]> wrote: Hi All, in my setting.xml I have two profiles for two project categories. Is it possible to select the profile to use in the pom.xml file so that for any project there is no way to use the wrong profile ? Thanks in advance ste - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stefano Nichele Funambol Servers Tech Lead funambol :: mobile open source :: http://www.funambol.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: selecting profile in the pom.xml file
Yes. I add this at the bottom of my settings.xml: local-baselogic tomcat5.5 On Sat, May 31, 2008 at 7:48 AM, Stefano Nichele <[EMAIL PROTECTED]> wrote: > Hi All, > in my setting.xml I have two profiles for two project categories. Is it > possible to select the profile to use in the pom.xml file so that for any > project there is no way to use the wrong profile ? > > Thanks in advance > ste > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
selecting profile in the pom.xml file
Hi All, in my setting.xml I have two profiles for two project categories. Is it possible to select the profile to use in the pom.xml file so that for any project there is no way to use the wrong profile ? Thanks in advance ste - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to better manage cascading releases
We have a four uber project set of releases. We use scripts to check out the latest released pom.xml for each from svn, pull out the version number, step back if it's a -SNAPSHOT, update our module's dependencies to this version, run maven with the integration tests and check in the updated pom.xml if the tests pass before doing mvn release:prepare release:perform -B This is set up as a number of release jobs in Hudson. Just kick off a build and you get the release when it's all done, or an email telling you what broke... I would like to do a bit more work and make it keep trying less new versions of the dependency until it falls back to the one it started with... but that's getting too fancy... the script is currently only 100 or so lines long -Stephen On Fri, May 30, 2008 at 9:12 AM, Bracewell, Robert <[EMAIL PROTECTED]> wrote: > In our organization it depends on the project but I have projects that > release twice a week internally. Other groups or projects that are > reliant on such artifacts can then decide as and when they want to > depend on the new artifacts that were deployed. > > -Original Message- > From: Geoffrey Wiseman [mailto:[EMAIL PROTECTED] > Sent: 30 May 2008 03:35 > To: Maven Users List > Subject: Re: How to better manage cascading releases > > On Thu, May 29, 2008 at 6:39 PM, Michael McCallum <[EMAIL PROTECTED]> > wrote: > > > release early release often... we don't use snapshot dependencies and > > release > > artifacts early. So if you are working on one of the 13 dependent > libraries > > as soon as you - the dev - is happy the change is ready for use then > you > > release it. why leave it as a snapshot? If the change would break > anything > > useing it we bump the major version up so its not pulled in until > > downstream > > users are ready. > > > > if you use version ranges and manage codelines by major version then > you > > can > > easily have the trunk of a project being actively developed and > released > > without pulling it into a deliverable. > > > Hmm, interesting perspective. > > I still find it takes an hour or two to pull off a release, between the > dry-run, the actual prepare and the perform -- do you find that cost > goes > down if you release a lot, or have tricks for reducing the cost of > releasing? > > - Geoffrey > -- > Geoffrey Wiseman > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Q: Best Approach for Packaging Static and Dynamic Web Content?
Hi. I currently have two (maven) projects which represent a single WAR. Currently, the WAR is assembled via ANT in the second project. Our requirements are to use Maven to continue to support the separation: 1. A jar project for static content for web application: *.js, *.html (for web designers) 2. A war project for the dynamic content: (for java/jsp developers) For the jar application, it's a regular maven application project where I store my content under /src/main/resources. I then created an assembly to pack the files into a .zip archive, storing the content at /. I thought, the second project could pull in that static content and store it at /src/main/webapp, but I'm not sure how to do it elegantly in maven or what the best practice would be? Built-in plugin? Custom assembly? Attach at which phase? My questions are: - What is the best way to structure the two projects (mainly the static content) - What is the best way to pull in the static content, during assembly, in the war (web) application project? - Would I benefit from a parent/child project or module relationship? - Could you provide me some examples? Any of your thoughts and help will be greatly appreciated. (I'm actively reading as much as I can on my own, but I'm under a time constraint.) Thank you, George Craig -- View this message in context: http://www.nabble.com/Q%3A-Best-Approach-for-Packaging-Static-and-Dynamic-Web-Content--tp17572801p17572801.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
