how to get maven 2.0.9 to use local repository
Hallo! I am using maven on openSUSE 11 to create an appfuse project with the following command: *mvn* archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-basic-struts -DarchetypeVersion=2.0.2 -DgroupId=*com.oci.sample* -DartifactId=*timeEntry *The command works ok and retrieves the dependencies. Checking in ~/.m2/repository, I can find the files that have been downloaded. On creating a similar project with a different name but in offline mode, I get the following error: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found Yet searching the repository shows the following: * [EMAIL PROTECTED]:~ find .m2/ -name 'maven-archetype-plugin*'* .m2/repository/org/apache/maven/plugins/maven-archetype-plugin .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom.sha1 .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar.sha1 Please tell me how I can use the local repository and avoid going online.
Re: how to get maven 2.0.9 to use local repository
It sounds like the issue is that you have something else forcing the archetype version on you. can you check and see if mvn -o org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-3:create works for you? If that works for you then what's happening is that a pom is locking down the version to a version that you have not downloaded yet. 2008/9/23 Eric Njogu [EMAIL PROTECTED] Hallo! I am using maven on openSUSE 11 to create an appfuse project with the following command: *mvn* archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-basic-struts -DarchetypeVersion=2.0.2 -DgroupId=*com.oci.sample* -DartifactId=*timeEntry *The command works ok and retrieves the dependencies. Checking in ~/.m2/repository, I can find the files that have been downloaded. On creating a similar project with a different name but in offline mode, I get the following error: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found Yet searching the repository shows the following: * [EMAIL PROTECTED]:~ find .m2/ -name 'maven-archetype-plugin*'* .m2/repository/org/apache/maven/plugins/maven-archetype-plugin .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom.sha1 .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar.sha1 Please tell me how I can use the local repository and avoid going online.
Re: Creating first Maven Project-Problem
Hey Thanks for the reply. Do I hve to do that for all the tags or just for the proxy one??Would appreciate ur help Stephen Connolly-2 wrote: You need to remove the comment start and end markers !-- and -- If you look carefully you'll see you have your lovely proxies definintion ignored inside a comment 2008/9/22 ashleyvijay [EMAIL PROTECTED] Thanks for the reply. I didnt hve a settings.xml in .m2 directory so i copied the settings.xml from apache-maven-2.0.9\conf and pasted it into .m2 directory and changed the proxy settings a little according the link which u gave to me. So the proxy part in settings.xml looks like this. I tried to create the first project again but still doesnt work. Would apprecaite for ur help. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol hosthttp-proxy.zx.basf-ag.de/host port8080/port /proxy -- /proxies mylene wrote: see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19608218.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] -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19622533.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]
Re: Creating first Maven Project-Problem
try thinking about it tags that are commented out are ignored have you anything else in there that you doin't want ignored? 2008/9/23 ashleyvijay [EMAIL PROTECTED] Hey Thanks for the reply. Do I hve to do that for all the tags or just for the proxy one??Would appreciate ur help Stephen Connolly-2 wrote: You need to remove the comment start and end markers !-- and -- If you look carefully you'll see you have your lovely proxies definintion ignored inside a comment 2008/9/22 ashleyvijay [EMAIL PROTECTED] Thanks for the reply. I didnt hve a settings.xml in .m2 directory so i copied the settings.xml from apache-maven-2.0.9\conf and pasted it into .m2 directory and changed the proxy settings a little according the link which u gave to me. So the proxy part in settings.xml looks like this. I tried to create the first project again but still doesnt work. Would apprecaite for ur help. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol hosthttp-proxy.zx.basf-ag.de/host port8080/port /proxy -- /proxies mylene wrote: see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO] C:\ -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607304.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19607766.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] -- Mylene -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19608218.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] -- View this message in context: http://www.nabble.com/Creating-first-Maven-Project-Problem-tp19607304p19622533.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL
Re: how to get maven 2.0.9 to use local repository
Thanks Stephen, This is the resulting error message when I do as you suggested: Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-archetype-plugin Reason: POM 'org.apache.maven.plugins:maven-archetype-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-archetype-plugin:pom:2.0-alpha-3 for project org.apache.maven.plugins:maven-archetype-plugin On Tue, Sep 23, 2008 at 10:03 AM, Stephen Connolly [EMAIL PROTECTED] wrote: It sounds like the issue is that you have something else forcing the archetype version on you. can you check and see if mvn -o org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-3:create works for you? If that works for you then what's happening is that a pom is locking down the version to a version that you have not downloaded yet. 2008/9/23 Eric Njogu [EMAIL PROTECTED] Hallo! I am using maven on openSUSE 11 to create an appfuse project with the following command: *mvn* archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-basic-struts -DarchetypeVersion=2.0.2 -DgroupId=*com.oci.sample* -DartifactId=*timeEntry *The command works ok and retrieves the dependencies. Checking in ~/.m2/repository, I can find the files that have been downloaded. On creating a similar project with a different name but in offline mode, I get the following error: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found Yet searching the repository shows the following: * [EMAIL PROTECTED]:~ find .m2/ -name 'maven-archetype-plugin*'* .m2/repository/org/apache/maven/plugins/maven-archetype-plugin .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom.sha1 .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar.sha1 Please tell me how I can use the local repository and avoid going online.
verbosetrue/verbose is ignored for maven-compiler-plugin
I don't see the effect of verbosetrue/verbose. When I run with -X, I do see that verbose = true, but I don't see it being passed to javac. I tried with fork = true and the command line that was used to invoke javac did not have verbose option set. I am using default compiler. Thanks, Sahoo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating first Maven Project-Problem
Perhaps that was a little bit harsh of a reply... I'll try again. In Maven, there is an overriding principle of convention over configuration. Which basically put is Tell maven only that which you want done differently from the defaults (If you like, ANT has the philosophy of Tell me _exactly_ what you want to do) The simplest example of this is that in Maven, if you want to build a jar file, you start with a simplest pom file that specifies just the groupId, artifactId and vesion: project groupIdcom.foo.test/groupId artifactIdbar/artifactId version1.0-SNAPSHOT/version /project When maven sees this it takes everything that you have not said and substitutes the bits from the super pom in. (Strictly speaking this is not true, maven starts with the super pom and adds or updates as necessary the bits from your pom) The same applies with the settings.xml file. Maven has an internal default settings.xml... it then applies any changes from the settings.xml in MAVEN_HOME, and finally applies any changes from your user settings.xml. You may have noticed in the global settings.xml file that every section is commented out... that's because maven is using the default settings.xml stored internally... The commented sections are to illustrate what you can put in a settings.xml. If all you want to tell Maven is that it should use a proxy, then all you need is the proxy section if you want to tell maven some other stuff as well, then you should have those sections uncommented too. -Stephen 2008/9/23 Stephen Connolly [EMAIL PROTECTED] try thinking about it tags that are commented out are ignored have you anything else in there that you doin't want ignored? 2008/9/23 ashleyvijay [EMAIL PROTECTED] Hey Thanks for the reply. Do I hve to do that for all the tags or just for the proxy one??Would appreciate ur help Stephen Connolly-2 wrote: You need to remove the comment start and end markers !-- and -- If you look carefully you'll see you have your lovely proxies definintion ignored inside a comment 2008/9/22 ashleyvijay [EMAIL PROTECTED] Thanks for the reply. I didnt hve a settings.xml in .m2 directory so i copied the settings.xml from apache-maven-2.0.9\conf and pasted it into .m2 directory and changed the proxy settings a little according the link which u gave to me. So the proxy part in settings.xml looks like this. I tried to create the first project again but still doesnt work. Would apprecaite for ur help. proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol hosthttp-proxy.zx.basf-ag.de/host port8080/port /proxy -- /proxies mylene wrote: see: http://maven.apache.org/guides/mini/guide-proxies.html Mylène On Mon, Sep 22, 2008 at 3:17 PM, ashleyvijay [EMAIL PROTECTED] wrote: Well I think so...if thats the case what should I do?? mylene wrote: Hi, Do you happen to work from behind a proxy that you didn't set (in settings.xml)? Mylène On Mon, Sep 22, 2008 at 2:47 PM, ashleyvijay [EMAIL PROTECTED] wrote: Hi all, Sorry if this question has been asked before. Im new to Maven and I hope I hve installed as per the instructions. When I try to create a new project it gives me this error. Can anybody please tell me how it could be resolved? C:\mvn --version Maven version: 2.0.9 Java version: 1.5.0_16 OS name: windows xp version: 5.1 arch: x86 Family: windows C:\mvn archetype:create\ -DarchetypeGroupId=org.apache.maven.archetypes\ -Dgrou p=com.mycompany.app\ -DartifactId=my-app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retri eved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exi st or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Sep 22 14:44:02 CEST 2008 [INFO] Final Memory: 1M/2M [INFO]
Re: how to get maven 2.0.9 to use local repository
Well then, that is telling you that the file you think is in your repository actually is not. Looks like you did not download it like you thought... or perhaps the md5 sums or sha1 sums do not match... Try that command again only in online mode (i.e. without the -o) 2008/9/23 Eric Njogu [EMAIL PROTECTED] Thanks Stephen, This is the resulting error message when I do as you suggested: Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-archetype-plugin Reason: POM 'org.apache.maven.plugins:maven-archetype-plugin' not found in repository: System is offline. org.apache.maven.plugins:maven-archetype-plugin:pom:2.0-alpha-3 for project org.apache.maven.plugins:maven-archetype-plugin On Tue, Sep 23, 2008 at 10:03 AM, Stephen Connolly [EMAIL PROTECTED] wrote: It sounds like the issue is that you have something else forcing the archetype version on you. can you check and see if mvn -o org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-3:create works for you? If that works for you then what's happening is that a pom is locking down the version to a version that you have not downloaded yet. 2008/9/23 Eric Njogu [EMAIL PROTECTED] Hallo! I am using maven on openSUSE 11 to create an appfuse project with the following command: *mvn* archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-basic-struts -DarchetypeVersion=2.0.2 -DgroupId=*com.oci.sample* -DartifactId=*timeEntry *The command works ok and retrieves the dependencies. Checking in ~/.m2/repository, I can find the files that have been downloaded. On creating a similar project with a different name but in offline mode, I get the following error: The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found Yet searching the repository shows the following: * [EMAIL PROTECTED]:~ find .m2/ -name 'maven-archetype-plugin*'* .m2/repository/org/apache/maven/plugins/maven-archetype-plugin .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.pom.sha1 .m2/repository/org/apache/maven/plugins/maven-archetype-plugin/2.0-alpha-3/maven-archetype-plugin-2.0-alpha-3.jar.sha1 Please tell me how I can use the local repository and avoid going online.
Re: Creating first Maven Project-Problem
Now my settings.xml looks like the following but when i try to create a
project it still doesnt work.I have edited the settings.xml as much as I
knw.Kindly help if Im missing something.
!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
License); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--
!--
| This is the configuration file for Maven. It can be specified at two
levels:
|
| 1. User Level. This settings.xml file provides configuration for a
single user,
| and is normally provided in $HOME/.m2/settings.xml.
|
| NOTE: This location can be overridden with the system
property:
|
|
-Dorg.apache.maven.user-settings=/path/to/user/settings.xml
|
| 2. Global Level. This settings.xml file provides configuration for all
maven
| users on a machine (assuming they're all using the same
maven
| installation). It's normally provided in
| ${maven.home}/conf/settings.xml.
|
| NOTE: This location can be overridden with the system
property:
|
|
-Dorg.apache.maven.global-settings=/path/to/global/settings.xml
|
| The sections in this sample file are intended to give you a running start
at
| getting the most out of your Maven installation. Where appropriate, the
default
| values (values used when the setting is not specified) are provided.
|
|--
settings
!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ~/.m2/repository
--
localRepositoryC:\Documents and
Settings\muthiaA\.m2\repository/localRepository
!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If
set to false,
| maven will use a sensible default value, perhaps based on some other
setting, for
| the parameter in question.
|
| Default: true
interactiveModetrue/interactiveMode
--
!-- offline
| Determines whether maven should attempt to connect to the network when
executing a build.
| This will have an effect on artifact downloads, artifact deployment,
and others.
|
| Default: false
--
offlinetrue/offline
!-- proxies
| This is a list of proxies which can be used on this machine to connect
to the network.
| Unless otherwise specified (by system property or command-line switch),
the first proxy
| specification in this list marked as active will be used.
|--
proxies
| Specification for one proxy, to be used in connecting to the network.
|
proxy
idoptional/id
activetrue/active
protocolhttp/protocol
hostlocalhost/host
port8080/port
nonProxyHostswww.google.com/nonProxyHosts
/proxy
/proxies
!-- servers
| This is a list of authentication profiles, keyed by the server-id used
within the system.
| Authentication profiles can be used whenever maven must make a
connection to a remote server.
|--
servers
!-- server
| Specifies the authentication information to use when connecting to a
particular server, identified by
| a unique name within the system (referred to by the 'id' attribute
below).
|
| NOTE: You should either specify username/password OR
privateKey/passphrase, since these pairings are
| used together.
|
server
iddeploymentRepo/id
usernamerepouser/username
passwordrepopwd/password
/server
--
!-- Another sample, using keys to authenticate.
server
idsiteServer/id
privateKey/path/to/private/key/privateKey
passphraseoptional; leave empty if not used./passphrase
/server
--
/servers
!-- mirrors
| This is a list of mirrors to be used in downloading artifacts from
remote repositories.
|
| It works like this: a POM may declare a repository to use in resolving
certain artifacts.
| However, this repository may have problems with heavy traffic at times,
so people have mirrored
| it to several places.
|
| That repository definition will have a unique id, so we can create a
mirror reference for that
| repository, to be used as an alternate download site. The mirror site
will be the preferred
| server for that repository.
|--
mirrors
!-- mirror
| Specifies a repository mirror site to use
Re: Creating first Maven Project-Problem
Start with just
settings
proxies
proxy
idoptional/id
activetrue/active
protocolhttp/protocol
hostlocalhost/host
port8080/port
/proxy
/proxies
/settings
Then see about adding in the rest of the stuff you need
BTW, you have www.google.com as a non-proxy host... why just google?
On 23 September 2008 08:55, ashleyvijay [EMAIL PROTECTED] wrote:
Now my settings.xml looks like the following but when i try to create a
project it still doesnt work.I have edited the settings.xml as much as I
knw.Kindly help if Im missing something.
!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
License); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
--
!--
| This is the configuration file for Maven. It can be specified at two
levels:
|
| 1. User Level. This settings.xml file provides configuration for a
single user,
| and is normally provided in $HOME/.m2/settings.xml.
|
| NOTE: This location can be overridden with the system
property:
|
|
-Dorg.apache.maven.user-settings=/path/to/user/settings.xml
|
| 2. Global Level. This settings.xml file provides configuration for all
maven
| users on a machine (assuming they're all using the same
maven
| installation). It's normally provided in
| ${maven.home}/conf/settings.xml.
|
| NOTE: This location can be overridden with the system
property:
|
|
-Dorg.apache.maven.global-settings=/path/to/global/settings.xml
|
| The sections in this sample file are intended to give you a running
start
at
| getting the most out of your Maven installation. Where appropriate, the
default
| values (values used when the setting is not specified) are provided.
|
|--
settings
!-- localRepository
| The path to the local repository maven will use to store artifacts.
|
| Default: ~/.m2/repository
--
localRepositoryC:\Documents and
Settings\muthiaA\.m2\repository/localRepository
!-- interactiveMode
| This will determine whether maven prompts you when it needs input. If
set to false,
| maven will use a sensible default value, perhaps based on some other
setting, for
| the parameter in question.
|
| Default: true
interactiveModetrue/interactiveMode
--
!-- offline
| Determines whether maven should attempt to connect to the network when
executing a build.
| This will have an effect on artifact downloads, artifact deployment,
and others.
|
| Default: false
--
offlinetrue/offline
!-- proxies
| This is a list of proxies which can be used on this machine to connect
to the network.
| Unless otherwise specified (by system property or command-line switch),
the first proxy
| specification in this list marked as active will be used.
|--
proxies
| Specification for one proxy, to be used in connecting to the network.
|
proxy
idoptional/id
activetrue/active
protocolhttp/protocol
hostlocalhost/host
port8080/port
nonProxyHostswww.google.com/nonProxyHosts
/proxy
/proxies
!-- servers
| This is a list of authentication profiles, keyed by the server-id used
within the system.
| Authentication profiles can be used whenever maven must make a
connection to a remote server.
|--
servers
!-- server
| Specifies the authentication information to use when connecting to a
particular server, identified by
| a unique name within the system (referred to by the 'id' attribute
below).
|
| NOTE: You should either specify username/password OR
privateKey/passphrase, since these pairings are
| used together.
|
server
iddeploymentRepo/id
usernamerepouser/username
passwordrepopwd/password
/server
--
!-- Another sample, using keys to authenticate.
server
idsiteServer/id
privateKey/path/to/private/key/privateKey
passphraseoptional; leave empty if not used./passphrase
/server
--
/servers
!-- mirrors
| This is a list of mirrors to be used in downloading artifacts from
remote repositories.
|
| It works like this: a POM may declare a repository to use in resolving
certain artifacts.
| However, this repository may have problems
Re: eclipse plugin, resolve dependencies to the projects in the workspace
On Mon, Sep 22, 2008 at 01:47:13PM -0700, Eugene Kuleshov wrote: Eugeny N Dzhurinsky-2 wrote: I have the project A, which depends on the project B, both of the projects are located in the same workspace. ... I found there is the property workspace described in http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#workspace, however neither using it as mvn eclipse:eclipse -Dworkspace=/home/user/workspace, nor specifying it in the plugin configuration did not give the desired results, and the project B is still referenced as a JAR file in the local repository. Do I miss something? Out of curiosity, why don't you use Maven IDe integration, such as m2eclipse? http://m2eclipse.codehaus.org/ I just tried it and I was really impressed of it's capabilities. Many thanks! -- Eugene N Dzhurinsky pgpgV7m5XjXNq.pgp Description: PGP signature
scm:tag/branch doesn't update scm section
Hi, When executing scm:tag goal or scm:branch goal, I think that the plugin should add the tag in the scm section of the pom.xml. Why doesn't it do that ? Benoit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
{Disarmed} Antwort: Re: Antwort: Re: Attaching source zip to jar managed by maven
Actually it is not a bug in the m2eclipse plugin but an inaccurate use by me. After activating Download Artifact Sources under Window - Preferences AND choosing Download Sources in the context menu of the m2eclipse plugin the download and attachment of the sources had worked correctly. Von: Eugene Kuleshov [EMAIL PROTECTED] An: users@maven.apache.org Datum: 22.09.2008 22:54 Betreff: Re: Antwort: Re: Attaching source zip to jar managed by maven Olel wrote: sorry for being a little unprecise. It is not that I don't want to have the sources locally, but don't want to manage the attaching on every developer machine as you have guessed. Therefore I tried the m2eclipse feature Download Artifact Sources and give it a try with dbunit-2.2.3 from repo1.maven.org which has Javadoc and sources attached. Unfortunately that doesn't work. Neither are the sources downloaded nor attached to the local jar. Do you have any idea what might be the problem? Can you please submit a bug report to m2eclipse and provide simple test project that would allow to reproduce this issue with dbunit sources. http://jira.codehaus.org/browse/MNGECLIPSE Also note that there is Mave / Download Sources action that could be invoked on Maven projects or individual jars. Olel wrote: The other thing is: most of the jars we use do not have sources in the public repositories. Could you give me a short introduction on how to add these sources manually to our enterprise repository and attach to their jars? With m2eclipse you can attach sources and javadocs locally without deploying them to the Maven repository. You can do that from the jar properies dialog. regards, Eugene -- View this message in context: http://www.nabble.com/Attaching-source-zip-to-jar-managed-by-maven-tp19530862p19616052.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] -- engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack
scm:branch should fail if branch already exists.
Hi, When executing mvn scm:branch with an existing branch, the execution success without any warnings: - [INFO] [scm:branch] [INFO] Final Branch Name: 'test1' [INFO] Executing: /bin/sh -c cd /home/decherfb/tmp/testMavenComponentA1 cvs -z3 -f -q tag -b -F -c test1 [INFO] Working directory: /home/decherfb/tmp/testMavenComponentA1 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 29 seconds [INFO] Finished at: Tue Sep 23 11:17:04 CEST 2008 [INFO] Final Memory: 7M/15M [INFO] --- This is not correct. We should have a way to detect that the branch wasn't created. The execution of the cvs command give: --- [EMAIL PROTECTED] testMavenComponentA1]$ cvs -z3 -f -q tag -b -F -c test1 cvs tag: .cvsignore: Not moving branch tag `test1' from 1.1 to 1.1.0.8. cvs tag: pom.xml: Not moving branch tag `test1' from 1.22 to 1.22.0.4. cvs tag: testfile: Not moving branch tag `test1' from 1.1 to 1.1.0.8. cvs tag: src/main/java/com/kelkoo/test/App.java: Not moving branch tag `test1' from 1.4 to 1.4.0.8. cvs tag: src/test/java/com/kelkoo/test/AppTest.java: Not moving branch tag `test1' from 1.1 to 1.1.0.8. - The behaviour is correct using svn. Benoit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What's the point of listing all artifacts in archetype.xml?
I wanted to create my own archetype... I've prepared set of prototype sources which should be used as tempate for creating new project. According to document Guide to creating archetypes I should put them under src/main/resources/archetype-resources/. That's ok, I put them there. But then the user guide says that I have to put every prototype file name (with full path) into archetype.xml file! What for? (I gave up at this point, it is too much unnecessary work.) What's the point of such data redundancy? If I have the complete file structure under src/main/resources/archetype-resources/, then maven archetype plugin should simply copy it when creating project from archetype. Putting the list of those files in archetype.xml is waste of time. Can somebody explain me why it was designed so? -- View this message in context: http://www.nabble.com/What%27s-the-point-of-listing-all-artifacts-in-archetype.xml--tp19626976p19626976.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]
Re: {Disarmed} Antwort: Re: Antwort: Re: Attaching source zip to jar managed by maven
Olel wrote: Actually it is not a bug in the m2eclipse plugin but an inaccurate use by me. After activating Download Artifact Sources under Window - Preferences AND choosing Download Sources in the context menu of the m2eclipse plugin the download and attachment of the sources had worked correctly. Now I am confused. The download sources checkbox supposed to download sources automatically when you run Maven / Update Dependencies action or when that action is executed in other cases, like on first project import. The action like Maven / Download Sources is completely independent from that checkbox. regards, Eugene -- View this message in context: http://www.nabble.com/Attaching-source-zip-to-jar-managed-by-maven-tp19530862p19628848.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]
EJB Client Jars and WAR File..
Hi, Our Project set up is as follows. 1. EJB Project 1 2. EJB Project 2 3. EJB Project 3 EJB client jars are generated for the respective projects. Then we use an assembler to gather all files (What we call as iface package classes) and create a client jar. This client jar contains the EJB stubs + some VOs of all the 3 EJB Projects. This client jar file needs to be bundled in a WAR file. Now I am faced with a difficulty. Unless I install the client jar file as an ejb-client in Maven repository and declare the type as ejb-client in the dependency section of the WAR project's POM, I am not able to include it. I even gave a system scope and it's still not bundling it as a plain jar file. Is ejb-client the only way to include the jar file? Is there a way to include it as a plain jar (Some EJB code still resides inside the client jar) Regards, Ravi iGATE is Ranked No. 3 in DQ-IDC best IT employer survey and Ranked No.6 by Business Today-Mercer Human Resource Consulting-TNS in a cross industry survey of Best Companies to work for in India DISCLAIMER- Information transmitted by this EMAIL is proprietary to iGATE Group of Companies and is intended for use only by the individual or entity to whom it is addressed and may contain information that is privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient of this EMAIL immediately notify the sender at iGATE or [EMAIL PROTECTED] and delete this EMAIL including any attachments
Weird resources problem...
Hi, I have a resource I need filtered which used to sit in my src/main/resources. I moved it to my src/test/resources. I also adjusted the pom.xml: build resources resource directorysrc/test/resources/directory filteringtrue/filtering /resource /resources /build When this used to say 'directorysrc/main/resources/directory' and the resource was actually in the 'main', everything worked just fine. However, now, a very strange thing is happening. When I execute maven and look into the target directory, I find the following... The 'classes' directory actually has that resource there in its FILTERED version, while the 'test-classes' directory has that resource in its UNFILTERED version. I have done many cleans, so it's definitely not an old file. I am not even sure why it's inside 'classes' to begin with?! How did the resource from the test/resource end up inside the 'classes' directory? Any idea what I am doing wrong? Thanks, Yaakov. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Weird resources problem...
Ok, never mind I should have switched the tags to testResources... forgot all about that. On Tue, Sep 23, 2008 at 11:35 AM, Yaakov Chaikin [EMAIL PROTECTED] wrote: Hi, I have a resource I need filtered which used to sit in my src/main/resources. I moved it to my src/test/resources. I also adjusted the pom.xml: build resources resource directorysrc/test/resources/directory filteringtrue/filtering /resource /resources /build When this used to say 'directorysrc/main/resources/directory' and the resource was actually in the 'main', everything worked just fine. However, now, a very strange thing is happening. When I execute maven and look into the target directory, I find the following... The 'classes' directory actually has that resource there in its FILTERED version, while the 'test-classes' directory has that resource in its UNFILTERED version. I have done many cleans, so it's definitely not an old file. I am not even sure why it's inside 'classes' to begin with?! How did the resource from the test/resource end up inside the 'classes' directory? Any idea what I am doing wrong? Thanks, Yaakov. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating first Maven Project-Problem
Also, your settings.xml shows: offlinetrue/offline This will almost certainly cause you problems. Remove it. As Stephen says, the text he sent (proxy section) should be the only thing in your settings.xml file for now. Wayne On Tue, Sep 23, 2008 at 1:37 AM, Stephen Connolly [EMAIL PROTECTED] wrote: Start with just settings proxies proxy idoptional/id activetrue/active protocolhttp/protocol hostlocalhost/host port8080/port /proxy /proxies /settings Then see about adding in the rest of the stuff you need BTW, you have www.google.com as a non-proxy host... why just google? On 23 September 2008 08:55, ashleyvijay [EMAIL PROTECTED] wrote: Now my settings.xml looks like the following but when i try to create a project it still doesnt work.I have edited the settings.xml as much as I knw.Kindly help if Im missing something. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Filter
I am filtering and for some reason the filters do not work unless i do a chmod 777 on the file with tokens to be replaced. I am on Mac OS X 10.5 running pre-installed maven 2.0.6. Im guessing this might be priv thing but not 100% sure. Anyone run across this? -- View this message in context: http://www.nabble.com/Filter-tp19632125p19632125.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]
Re: Issues with Maven 2.1.0 resume from feature
Ok, thanks, I've misunderstood your blog post... and just seen the milestones here http://docs.codehaus.org/display/MAVEN/Maven+2.1.0+Release+Plan I'll get back to you on the dev list as soon as I have time to play with the reactor plugin. On Tue, Sep 23, 2008 at 4:18 AM, Brett Porter [EMAIL PROTECTED] wrote: This feature is scheduled for M2, which can be built from the maven-2.1.x branch, but was not included in the 2.1.0-M1 release. You can discuss this further on the Maven dev list. If you are interested in using the reactor functionality without upgrading Maven, you can try the reactor plugin which is currently being prepared for release. - Brett 2008/9/23 Henri Tremblay [EMAIL PROTECTED]: Arg.. forget the attachment (which I'm not even sure is going through) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - 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]
Packaging fails on EAR project
Hi all, I've trying to package a EAR application unsuccessfully. My pom.xml references a EJB module this way: dependency groupIdbr.gov.caixa.maven/groupId artifactIdAPPLICATION-ejb/artifactId version1.0/version scopeprovided/scope /dependency Everything seems ok, but I received the error below. There is an issue on jira ( http://jira.codehaus.org/browse/MRELEASE-129 http://jira.codehaus.org/browse/MRELEASE-129) describing this problem, but there is no solution yet. I wouldn't like to install the APPLICATION-ejb-1.0.jar artifact (I believe it's not the best thing to do) . How can I solve this problem? Please help me, I've tried all possible ways to find a solution... Thanks, Andre C:\Andre\Projetos\exemplo-mavenmvn clean package [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] project [INFO] enterprise java beans [INFO] java servlets [INFO] ear assembly [INFO] [INFO] Building project [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [site:attach-descriptor] [INFO] [INFO] Building enterprise java beans [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Andre\Projetos\exemplo-maven\ejbs\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 3 source files to C:\Andre\Projetos\exemplo-maven\ejbs\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [ejb:ejb] [INFO] Building ejb APPLICATION-ejb-1.0 with ejbVersion 2.1 [INFO] Building jar: C:\Andre\Projetos\exemplo-maven\ejbs\target\APPLICATION-ejb-1.0.jar [INFO] [INFO] Building java servlets [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repository.jboss.com/maven2//commons-chain/commons-chain/1.2/commons- chain-1.2.pom Downloading: http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/commons-chain- 1.2.pom Downloading: http://repository.jboss.com/maven2//br/gov/caixa/maven/APPLICATION-ejb/1.0/A PPLICATION-ejb-1.0.jar Downloading: http://repo1.maven.org/maven2/br/gov/caixa/maven/APPLICATION-ejb/1.0/APPLICA TION-ejb-1.0.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) br.gov.caixa.maven:APPLICATION-web:war:1.0 2) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 -- 1 required artifact is missing. for artifact: br.gov.caixa.maven:APPLICATION-web:war:1.0 from the specified remote repositories: repository.jboss.com (http://repository.jboss.com/maven2/), central (http://repo1.maven.org/maven2), maven2-snapshots.jboss.com (http://snapshots.jboss.com/) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Tue Sep 23 14:36:18 BRT 2008 [INFO] Final Memory: 13M/23M [INFO]
Re: What's the point of listing all artifacts in archetype.xml?
No clue why it was designed like this, but at least for me, creating an archetype is not an everyday thing so its really not a big deal to spend a little extra time when I occasionally need to build a new archetype or work on an existing one. With a little ls and sed/awk you can get all the files listed in the proper XML form right out of your command line. As with the rest of Maven, this is an open source project so you can post a JIRA and someone will consider adding the feature themselves or you can modify the code yourself and contribute it back to the project. Wayne On Tue, Sep 23, 2008 at 5:49 AM, Grzegorz Borkowski [EMAIL PROTECTED] wrote: I wanted to create my own archetype... I've prepared set of prototype sources which should be used as tempate for creating new project. According to document Guide to creating archetypes I should put them under src/main/resources/archetype-resources/. That's ok, I put them there. But then the user guide says that I have to put every prototype file name (with full path) into archetype.xml file! What for? (I gave up at this point, it is too much unnecessary work.) What's the point of such data redundancy? If I have the complete file structure under src/main/resources/archetype-resources/, then maven archetype plugin should simply copy it when creating project from archetype. Putting the list of those files in archetype.xml is waste of time. Can somebody explain me why it was designed so? -- View this message in context: http://www.nabble.com/What%27s-the-point-of-listing-all-artifacts-in-archetype.xml--tp19626976p19626976.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Packaging fails on EAR project
Maven needs all the dependencies you've declared to be available in your local repository (or in the module list somewhere under your current project) for a build to succeed. What is your reason for not wanting to install the EJB artifact? Why is it not the best thing to do?? Wayne On Tue, Sep 23, 2008 at 10:43 AM, Andre Dantas Rocha [EMAIL PROTECTED] wrote: Hi all, I've trying to package a EAR application unsuccessfully. My pom.xml references a EJB module this way: dependency groupIdbr.gov.caixa.maven/groupId artifactIdAPPLICATION-ejb/artifactId version1.0/version scopeprovided/scope /dependency Everything seems ok, but I received the error below. There is an issue on jira ( http://jira.codehaus.org/browse/MRELEASE-129 http://jira.codehaus.org/browse/MRELEASE-129) describing this problem, but there is no solution yet. I wouldn't like to install the APPLICATION-ejb-1.0.jar artifact (I believe it's not the best thing to do) . How can I solve this problem? Please help me, I've tried all possible ways to find a solution... Thanks, Andre C:\Andre\Projetos\exemplo-mavenmvn clean package [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] project [INFO] enterprise java beans [INFO] java servlets [INFO] ear assembly [INFO] [INFO] Building project [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [site:attach-descriptor] [INFO] [INFO] Building enterprise java beans [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Andre\Projetos\exemplo-maven\ejbs\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 3 source files to C:\Andre\Projetos\exemplo-maven\ejbs\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [ejb:ejb] [INFO] Building ejb APPLICATION-ejb-1.0 with ejbVersion 2.1 [INFO] Building jar: C:\Andre\Projetos\exemplo-maven\ejbs\target\APPLICATION-ejb-1.0.jar [INFO] [INFO] Building java servlets [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repository.jboss.com/maven2//commons-chain/commons-chain/1.2/commons- chain-1.2.pom Downloading: http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/commons-chain- 1.2.pom Downloading: http://repository.jboss.com/maven2//br/gov/caixa/maven/APPLICATION-ejb/1.0/A PPLICATION-ejb-1.0.jar Downloading: http://repo1.maven.org/maven2/br/gov/caixa/maven/APPLICATION-ejb/1.0/APPLICA TION-ejb-1.0.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) br.gov.caixa.maven:APPLICATION-web:war:1.0 2) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 -- 1 required artifact is missing. for artifact: br.gov.caixa.maven:APPLICATION-web:war:1.0 from the specified remote repositories: repository.jboss.com (http://repository.jboss.com/maven2/), central (http://repo1.maven.org/maven2), maven2-snapshots.jboss.com (http://snapshots.jboss.com/) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Tue Sep 23 14:36:18 BRT 2008 [INFO] Final Memory: 13M/23M [INFO]
RES: Packaging fails on EAR project
Problem solved using this code: dependency groupIdbr.gov.caixa.maven/groupId artifactIdAPPLICATION-ejb/artifactId version1.0/version scopecompile/scope typeejb/type /dependency -Mensagem original- De: Andre Dantas Rocha [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 23 de setembro de 2008 14:44 Para: users@maven.apache.org Assunto: Packaging fails on EAR project Hi all, I've trying to package a EAR application unsuccessfully. My pom.xml references a EJB module this way: dependency groupIdbr.gov.caixa.maven/groupId artifactIdAPPLICATION-ejb/artifactId version1.0/version scopeprovided/scope /dependency Everything seems ok, but I received the error below. There is an issue on jira ( http://jira.codehaus.org/browse/MRELEASE-129 http://jira.codehaus.org/browse/MRELEASE-129) describing this problem, but there is no solution yet. I wouldn't like to install the APPLICATION-ejb-1.0.jar artifact (I believe it's not the best thing to do) . How can I solve this problem? Please help me, I've tried all possible ways to find a solution... Thanks, Andre C:\Andre\Projetos\exemplo-mavenmvn clean package [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] project [INFO] enterprise java beans [INFO] java servlets [INFO] ear assembly [INFO] [INFO] Building project [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [site:attach-descriptor] [INFO] [INFO] Building enterprise java beans [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Andre\Projetos\exemplo-maven\ejbs\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 3 source files to C:\Andre\Projetos\exemplo-maven\ejbs\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [ejb:ejb] [INFO] Building ejb APPLICATION-ejb-1.0 with ejbVersion 2.1 [INFO] Building jar: C:\Andre\Projetos\exemplo-maven\ejbs\target\APPLICATION-ejb-1.0.jar [INFO] [INFO] Building java servlets [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repository.jboss.com/maven2//commons-chain/commons-chain/1.2/commons- chain-1.2.pom Downloading: http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/commons-chain- 1.2.pom Downloading: http://repository.jboss.com/maven2//br/gov/caixa/maven/APPLICATION-ejb/1.0/A PPLICATION-ejb-1.0.jar Downloading: http://repo1.maven.org/maven2/br/gov/caixa/maven/APPLICATION-ejb/1.0/APPLICA TION-ejb-1.0.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) br.gov.caixa.maven:APPLICATION-web:war:1.0 2) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 -- 1 required artifact is missing. for artifact: br.gov.caixa.maven:APPLICATION-web:war:1.0 from the specified remote repositories: repository.jboss.com (http://repository.jboss.com/maven2/), central (http://repo1.maven.org/maven2), maven2-snapshots.jboss.com (http://snapshots.jboss.com/) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Tue Sep 23 14:36:18 BRT 2008 [INFO] Final Memory: 13M/23M [INFO]
Maven Site / Compile Failure
When we run 'mvn clean install' in a particular project, all is well, compilation and all. When we run 'mvn clean install site' on that same project, we get a compilation error, seemingly due to one of the dependencies not being included. This is true on two different environments, and with both mvn 2.0.9 and mvn 2.1.0-M1 (although possibly not with mvn 2.0.8, although that may simply be due to the plugin versions changing, for all I know). I'm still diagnosing, but in the meantime, if anyone has any thoughts on what might be happening, I'm happy to hear 'em. -- Geoffrey Wiseman
deploy goal no longer deploying
Hi all, I am fairly new to maven but have had it working for almost a year with no real issues. Today I was trying to fix my build problem in continuum and found out it was maven or a plugin that has possibly changed behavior. I run a build on about 30 modules from continuum and use a command from continuum like... mvn -e -Ddeploylocation=file:///home/apache/ci_repo clean deploy Running the same maven command manually gets this same behavior as continuum does. I noticed that the last time the files in that tree were updated was the 9/19/2008. I also found that the jars I was successfully creating were in their respective workspace/target directories. They were no longer getting copied to the -Ddeploylocation= directory. Instead I am seeing this at the end of my build logs. . [INFO] [install:install] [INFO] [MAVEN-CORE-IT-LOG] Using output file path: target/install-install.txt [INFO] [MAVEN-CORE-IT-LOG] Creating output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt [INFO] [MAVEN-CORE-IT-LOG] Created output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt [INFO] [deploy:deploy] [INFO] [MAVEN-CORE-IT-LOG] Using output file path: target/deploy-deploy.txt [INFO] [MAVEN-CORE-IT-LOG] Creating output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt [INFO] [MAVEN-CORE-IT-LOG] Created output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 minutes 16 seconds [INFO] Finished at: Tue Sep 23 12:33:32 EDT 2008 [INFO] Final Memory: 63M/233M [INFO] Those deploy-deploy.txt and install-install.txt files are all zero bytes. Help? I am at a loss as to what I need to adjust to get the previous behavior of the copy. My guess is that a plugin was updated and I got the new functions. I am trying to nail down my version info in my poms but it takes time. I am using Maven 2.0.8 and a 1.5 jdk. thanks, Scott -- View this message in context: http://www.nabble.com/deploy-goal-no-longer-deploying-tp19634893p19634893.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]
Re: What's the point of listing all artifacts in archetype.xml?
One (albeit silly reason) is that you would not want the .svn and .CVS subdirectories getting added as well Though at the very least it could offer a goal to generate the archetype.xml by scanning the directory for you... and then you could massage the file by hand removing the stuff that should not be there -Stephen 2008/9/23 Wayne Fay [EMAIL PROTECTED] No clue why it was designed like this, but at least for me, creating an archetype is not an everyday thing so its really not a big deal to spend a little extra time when I occasionally need to build a new archetype or work on an existing one. With a little ls and sed/awk you can get all the files listed in the proper XML form right out of your command line. As with the rest of Maven, this is an open source project so you can post a JIRA and someone will consider adding the feature themselves or you can modify the code yourself and contribute it back to the project. Wayne On Tue, Sep 23, 2008 at 5:49 AM, Grzegorz Borkowski [EMAIL PROTECTED] wrote: I wanted to create my own archetype... I've prepared set of prototype sources which should be used as tempate for creating new project. According to document Guide to creating archetypes I should put them under src/main/resources/archetype-resources/. That's ok, I put them there. But then the user guide says that I have to put every prototype file name (with full path) into archetype.xml file! What for? (I gave up at this point, it is too much unnecessary work.) What's the point of such data redundancy? If I have the complete file structure under src/main/resources/archetype-resources/, then maven archetype plugin should simply copy it when creating project from archetype. Putting the list of those files in archetype.xml is waste of time. Can somebody explain me why it was designed so? -- View this message in context: http://www.nabble.com/What%27s-the-point-of-listing-all-artifacts-in-archetype.xml--tp19626976p19626976.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Site / Compile Failure
On Tue, Sep 23, 2008 at 3:01 PM, Geoffrey Wiseman [EMAIL PROTECTED] wrote: When we run 'mvn clean install' in a particular project, all is well, compilation and all. When we run 'mvn clean install site' on that same project, we get a compilation error, seemingly due to one of the dependencies not being included. This is true on two different environments, and with both mvn 2.0.9 and mvn 2.1.0-M1 (although possibly not with mvn 2.0.8, although that may simply be due to the plugin versions changing, for all I know). I'm still diagnosing, but in the meantime, if anyone has any thoughts on what might be happening, I'm happy to hear 'em. Seems to be some weird interaction between the classpath and the site plugin in a multimodule. Basically, I've got a structure somewhat like this within some part of my project structure: model - persistence - service Model contains some domain model classes, but the tests contain a few builders for model classes that help make tests easier to write. Accordingly, the persistence module depends both on the model (main artifact, compile scope) and the model tests (test classifier, test scope). The service code relies on some of those model classes. When you run mvn clean install on the whole thing, it's fine. When you run mvn clean install site on the whole thing, the service module doesn't include the model main artifact (project or JAR) on the compile classpath, and fails. If you run mvn clean install site on the service module alone, it's fine. If I get a chance, I'll put together an example project. In the meantime, I'll probably just put the builders in the main source tree for now - seems to make the problem go away. - Geoffrey -- Geoffrey Wiseman
Eclipse WTP exported resources?
I've encountered a problem where doing an eclipse:eclipse on an Eclipse WTP project doesn't properly export classpath resources. I think I read on a list or forum somewhere that this was a known bug, but I don't recall seeing a workaround or anything. Does anyone know if there is a solution to this problem? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: Packaging fails on EAR project
Hi Wayne, This EJB will be used only in this project, and I will re-package it every time. Because of this I believe it is not the best option to do. (it's my opinion, but I just started using Maven) Andre -Mensagem original- De: Wayne Fay [mailto:[EMAIL PROTECTED] Enviada em: terça-feira, 23 de setembro de 2008 15:34 Para: Maven Users List Assunto: Re: Packaging fails on EAR project Maven needs all the dependencies you've declared to be available in your local repository (or in the module list somewhere under your current project) for a build to succeed. What is your reason for not wanting to install the EJB artifact? Why is it not the best thing to do?? Wayne On Tue, Sep 23, 2008 at 10:43 AM, Andre Dantas Rocha [EMAIL PROTECTED] wrote: Hi all, I've trying to package a EAR application unsuccessfully. My pom.xml references a EJB module this way: dependency groupIdbr.gov.caixa.maven/groupId artifactIdAPPLICATION-ejb/artifactId version1.0/version scopeprovided/scope /dependency Everything seems ok, but I received the error below. There is an issue on jira ( http://jira.codehaus.org/browse/MRELEASE-129 http://jira.codehaus.org/browse/MRELEASE-129) describing this problem, but there is no solution yet. I wouldn't like to install the APPLICATION-ejb-1.0.jar artifact (I believe it's not the best thing to do) . How can I solve this problem? Please help me, I've tried all possible ways to find a solution... Thanks, Andre C:\Andre\Projetos\exemplo-mavenmvn clean package [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] project [INFO] enterprise java beans [INFO] java servlets [INFO] ear assembly [INFO] [INFO] Building project [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [site:attach-descriptor] [INFO] [INFO] Building enterprise java beans [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] Deleting directory C:\Andre\Projetos\exemplo-maven\ejbs\target [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 3 source files to C:\Andre\Projetos\exemplo-maven\ejbs\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] No tests to run. [INFO] [ejb:ejb] [INFO] Building ejb APPLICATION-ejb-1.0 with ejbVersion 2.1 [INFO] Building jar: C:\Andre\Projetos\exemplo-maven\ejbs\target\APPLICATION-ejb-1.0.jar [INFO] [INFO] Building java servlets [INFO]task-segment: [clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://repository.jboss.com/maven2//commons-chain/commons-chain/1.2/commons- chain-1.2.pom Downloading: http://repo1.maven.org/maven2/commons-chain/commons-chain/1.2/commons-chain- 1.2.pom Downloading: http://repository.jboss.com/maven2//br/gov/caixa/maven/APPLICATION-ejb/1.0/A PPLICATION-ejb-1.0.jar Downloading: http://repo1.maven.org/maven2/br/gov/caixa/maven/APPLICATION-ejb/1.0/APPLICA TION-ejb-1.0.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=br.gov.caixa.maven -DartifactId=APPLICATION-ejb -Dversion=1.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) br.gov.caixa.maven:APPLICATION-web:war:1.0 2) br.gov.caixa.maven:APPLICATION-ejb:jar:1.0 -- 1 required artifact is missing. for artifact: br.gov.caixa.maven:APPLICATION-web:war:1.0 from the specified remote repositories: repository.jboss.com (http://repository.jboss.com/maven2/), central (http://repo1.maven.org/maven2), maven2-snapshots.jboss.com
Purpose and Status of 'stage' Plugin
Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Purpose and Status of 'stage' Plugin
(As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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]
SourceForge.net shell changes and repository syncing
SourceForge.net made changes to their shell services recently http://sourceforge.net/community/forum/topic.php?id=3518page Does this affect repository syncing in any way, or are the instructions in the mini-guide still valid? http://maven.apache.org/guides/mini/guide-central-repository-upload.html Thanks Mirko
RE: Purpose and Status of 'stage' Plugin
doesnt appear to work (properly) Note: Although it looks like we are only copying version 2.0.3, we are in fact copying everything from the source URL to the target. This is due to a bug and will change in the future. for now i would suggest using plain cp / (remote)rcp / (secure)scp Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: Purpose and Status of 'stage' Plugin Date: Tue, 23 Sep 2008 15:38:51 -0500 From: [EMAIL PROTECTED] To: users@maven.apache.org Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Get more out of the Web. Learn 10 hidden secrets of Windows Live. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008
Re: frustration with testNG tests running twice.
What doe you mean *default location* ? Do you mean package names? On Mon, Sep 22, 2008 at 7:59 PM, Brett Porter [EMAIL PROTECTED]wrote: They are probably in the default location so the default configuration runs them in the test phase. - Brett 2008/9/20 Mick Knutson [EMAIL PROTECTED]: I have this declaration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution execution idintegration-tests/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnoretrue/testFailureIgnore suiteXmlFiles suiteXmlFilesrc/test/resources/testng-functional.xml/suiteXmlFile /suiteXmlFiles groupssuite-init,database,functional,selenium/groups excludeGroupsunit/excludeGroups /configuration /execution /executions /plugin Now I even commented out the phasetest/phase to stop unit test from running, but they run anyways. And because there is not a testng.xml for that phase, the tests fail. Can someone please help me get just my functional tests to run in the phaseintegration-test/phase ??? Your help is greatly appreciated! -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com
Re: deploy goal no longer deploying
I just figured out I seem to be picking up this ... [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:0.1-stub-SNAPSHOT:runtime (selected for runtime) Now, I have specified every plugin declared in my pom to release versions. How do I get this one forced out? I have ... plugin artifactIdmaven-deploy-plugin/artifactId version2.4/version /plugin ... defined also. Seems to be ignoring it. Scott smitherz wrote: Hi all, I am fairly new to maven but have had it working for almost a year with no real issues. Today I was trying to fix my build problem in continuum and found out it was maven or a plugin that has possibly changed behavior. I run a build on about 30 modules from continuum and use a command from continuum like... mvn -e -Ddeploylocation=file:///home/apache/ci_repo clean deploy Running the same maven command manually gets this same behavior as continuum does. I noticed that the last time the files in that tree were updated was the 9/19/2008. I also found that the jars I was successfully creating were in their respective workspace/target directories. They were no longer getting copied to the -Ddeploylocation= directory. Instead I am seeing this at the end of my build logs. . [INFO] [install:install] [INFO] [MAVEN-CORE-IT-LOG] Using output file path: target/install-install.txt [INFO] [MAVEN-CORE-IT-LOG] Creating output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt [INFO] [MAVEN-CORE-IT-LOG] Created output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt [INFO] [deploy:deploy] [INFO] [MAVEN-CORE-IT-LOG] Using output file path: target/deploy-deploy.txt [INFO] [MAVEN-CORE-IT-LOG] Creating output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt [INFO] [MAVEN-CORE-IT-LOG] Created output file: /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 minutes 16 seconds [INFO] Finished at: Tue Sep 23 12:33:32 EDT 2008 [INFO] Final Memory: 63M/233M [INFO] Those deploy-deploy.txt and install-install.txt files are all zero bytes. Help? I am at a loss as to what I need to adjust to get the previous behavior of the copy. My guess is that a plugin was updated and I got the new functions. I am trying to nail down my version info in my poms but it takes time. I am using Maven 2.0.8 and a 1.5 jdk. thanks, Scott -- View this message in context: http://www.nabble.com/deploy-goal-no-longer-deploying-tp19634893p19636766.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]
Re: Maven Site / Compile Failure
On Tue, Sep 23, 2008 at 3:56 PM, Geoffrey Wiseman [EMAIL PROTECTED] wrote: Seems to be some weird interaction between the classpath and the site plugin in a multimodule. Basically, I've got a structure somewhat like this within some part of my project structure: model - persistence - service Model contains some domain model classes, but the tests contain a few builders for model classes that help make tests easier to write. Accordingly, the persistence module depends both on the model (main artifact, compile scope) and the model tests (test classifier, test scope). The service code relies on some of those model classes. When you run mvn clean install on the whole thing, it's fine. When you run mvn clean install site on the whole thing, the service module doesn't include the model main artifact (project or JAR) on the compile classpath, and fails. If you run mvn clean install site on the service module alone, it's fine. If I get a chance, I'll put together an example project. In the meantime, I'll probably just put the builders in the main source tree for now - seems to make the problem go away. Simple example project using the terms in this email exhibits the same behavior. http://jira.codehaus.org/browse/MNG-3763 -- Geoffrey Wiseman
Re: Purpose and Status of 'stage' Plugin
At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the entire staging repo to a officially one. if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay [EMAIL PROTECTED] wrote: (As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Purpose and Status of 'stage' Plugin
So it sounds like your 'staging' repo is for a semi-formal QA process, like what we call User Acceptance Test [UAT] and the plugin is used to promote the entire repository to a final/production repo. But you promote the entire repo -- wouldn't it be better to have the ability to promote at a finer-grained level? I.e. at the artifact level? I'm looking to fit the maven repo deployment/release model into a scheme where Apache continuum builds run nightly and resulting artifacts are deployed to a specific QA repository. Certain WAR artifacts are suitable for testing and any arbitrary one may be deemed fit for UAT. It would be ideal to be able to promote an artifact [without having to rebuild it] and to redeploy it to a segregated repository. If approved in UAT, it could be promoted to production status [again without having to rebuild it]. QA and production folks would know that the artifact is *exactly* what had been built and qualified originally. Segregation is important, so we can demonstrate to auditors that a process attempts to prevent non-qualified apps from entering a production environment. Production staff can only pull artifacts from a specific repo and artifacts can enter that repo only under controlled conditions. I was hoping that the staging plugin could help somewhat in this by allowing us to move artifacts between repos. Brad -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 3:54 PM To: Maven Users List Subject: Re: Purpose and Status of 'stage' Plugin At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the entire staging repo to a officially one. if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay [EMAIL PROTECTED] wrote: (As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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] - 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: Purpose and Status of 'stage' Plugin
there already a JIRA for that. On Tue, Sep 23, 2008 at 2:34 PM, Harper, Brad [EMAIL PROTECTED] wrote: So it sounds like your 'staging' repo is for a semi-formal QA process, like what we call User Acceptance Test [UAT] and the plugin is used to promote the entire repository to a final/production repo. But you promote the entire repo -- wouldn't it be better to have the ability to promote at a finer-grained level? I.e. at the artifact level? I'm looking to fit the maven repo deployment/release model into a scheme where Apache continuum builds run nightly and resulting artifacts are deployed to a specific QA repository. Certain WAR artifacts are suitable for testing and any arbitrary one may be deemed fit for UAT. It would be ideal to be able to promote an artifact [without having to rebuild it] and to redeploy it to a segregated repository. If approved in UAT, it could be promoted to production status [again without having to rebuild it]. QA and production folks would know that the artifact is *exactly* what had been built and qualified originally. Segregation is important, so we can demonstrate to auditors that a process attempts to prevent non-qualified apps from entering a production environment. Production staff can only pull artifacts from a specific repo and artifacts can enter that repo only under controlled conditions. I was hoping that the staging plugin could help somewhat in this by allowing us to move artifacts between repos. Brad -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 3:54 PM To: Maven Users List Subject: Re: Purpose and Status of 'stage' Plugin At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the entire staging repo to a officially one. if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay [EMAIL PROTECTED] wrote: (As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Purpose and Status of 'stage' Plugin
[EMAIL PROTECTED] also has a maven-wagon-plugin currently in the sandbox. Give it a try and feedback On Tue, Sep 23, 2008 at 2:43 PM, Dan Tran [EMAIL PROTECTED] wrote: there already a JIRA for that. On Tue, Sep 23, 2008 at 2:34 PM, Harper, Brad [EMAIL PROTECTED] wrote: So it sounds like your 'staging' repo is for a semi-formal QA process, like what we call User Acceptance Test [UAT] and the plugin is used to promote the entire repository to a final/production repo. But you promote the entire repo -- wouldn't it be better to have the ability to promote at a finer-grained level? I.e. at the artifact level? I'm looking to fit the maven repo deployment/release model into a scheme where Apache continuum builds run nightly and resulting artifacts are deployed to a specific QA repository. Certain WAR artifacts are suitable for testing and any arbitrary one may be deemed fit for UAT. It would be ideal to be able to promote an artifact [without having to rebuild it] and to redeploy it to a segregated repository. If approved in UAT, it could be promoted to production status [again without having to rebuild it]. QA and production folks would know that the artifact is *exactly* what had been built and qualified originally. Segregation is important, so we can demonstrate to auditors that a process attempts to prevent non-qualified apps from entering a production environment. Production staff can only pull artifacts from a specific repo and artifacts can enter that repo only under controlled conditions. I was hoping that the staging plugin could help somewhat in this by allowing us to move artifacts between repos. Brad -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 3:54 PM To: Maven Users List Subject: Re: Purpose and Status of 'stage' Plugin At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the entire staging repo to a officially one. if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay [EMAIL PROTECTED] wrote: (As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: scm:tag/branch doesn't update scm section
Generally this is handled by release:prepare or release:branch. Someone asked this recently, so it's really a matter of having an issue with enough votes :) Perhaps if the POM-rewriting was factored out suitably it could be used in scm. - Brett 2008/9/23 Benoit Decherf [EMAIL PROTECTED]: Hi, When executing scm:tag goal or scm:branch goal, I think that the plugin should add the tag in the scm section of the pom.xml. Why doesn't it do that ? Benoit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: scm:branch should fail if branch already exists.
I suggest creating an issue in the SCM plugin regarding this also. Thanks, Brett 2008/9/23 Benoit Decherf [EMAIL PROTECTED]: Hi, When executing mvn scm:branch with an existing branch, the execution success without any warnings: - [INFO] [scm:branch] [INFO] Final Branch Name: 'test1' [INFO] Executing: /bin/sh -c cd /home/decherfb/tmp/testMavenComponentA1 cvs -z3 -f -q tag -b -F -c test1 [INFO] Working directory: /home/decherfb/tmp/testMavenComponentA1 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 29 seconds [INFO] Finished at: Tue Sep 23 11:17:04 CEST 2008 [INFO] Final Memory: 7M/15M [INFO] --- This is not correct. We should have a way to detect that the branch wasn't created. The execution of the cvs command give: --- [EMAIL PROTECTED] testMavenComponentA1]$ cvs -z3 -f -q tag -b -F -c test1 cvs tag: .cvsignore: Not moving branch tag `test1' from 1.1 to 1.1.0.8. cvs tag: pom.xml: Not moving branch tag `test1' from 1.22 to 1.22.0.4. cvs tag: testfile: Not moving branch tag `test1' from 1.1 to 1.1.0.8. cvs tag: src/main/java/com/kelkoo/test/App.java: Not moving branch tag `test1' from 1.4 to 1.4.0.8. cvs tag: src/test/java/com/kelkoo/test/AppTest.java: Not moving branch tag `test1' from 1.1 to 1.1.0.8. - The behaviour is correct using svn. Benoit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: frustration with testNG tests running twice.
2008/9/24 Mick Knutson [EMAIL PROTECTED]: What doe you mean *default location* ? Do you mean package names? src/test/java which would be picked up by default - do your tests reside in there? ie, if you comment out all the below and run mvn test, do they run? - Brett On Mon, Sep 22, 2008 at 7:59 PM, Brett Porter [EMAIL PROTECTED]wrote: They are probably in the default location so the default configuration runs them in the test phase. - Brett 2008/9/20 Mick Knutson [EMAIL PROTECTED]: I have this declaration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution execution idintegration-tests/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnoretrue/testFailureIgnore suiteXmlFiles suiteXmlFilesrc/test/resources/testng-functional.xml/suiteXmlFile /suiteXmlFiles groupssuite-init,database,functional,selenium/groups excludeGroupsunit/excludeGroups /configuration /execution /executions /plugin Now I even commented out the phasetest/phase to stop unit test from running, but they run anyways. And because there is not a testng.xml for that phase, the tests fail. Can someone please help me get just my functional tests to run in the phaseintegration-test/phase ??? Your help is greatly appreciated! -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Best Practice for code generation scenarios in Maven
I am currently porting an Ant-powered code generator to Maven and would like
to get input from this group for best practices with respect to code
generation in Maven.
Let's see if I have this right:
I wrote a Maven mojo to drive the code generator and can configure it in the
Maven project used for code generation.
I should always isolate the code generation into a single Maven module (this
could be part of a multi-module Maven project though) so that I can declare
the source directory for the generated code under the target directory.
For example, something like this would be declared in the module where code
generation takes place:
build
sourceDirectory${project.build.directory}/codegen/java/sourceDirectory
...
...
The jar file artifact resulting from the code generation module would only
contain class files from the generator.
Since the standard src/main/java sourceDirectory/ has been 'usurped' by
the source directory where the code generator wrote its code, I shouldn't
have any other Java code under src/main/java.
Does this sound correct? Is this the best practice for a Maven module for
code generation? Does anyone on this group do this differently than what I
sketched out here? If so, why and what are the advantages of your
alternative approach?
Thanks in advance for your input!
:handshake:
--
View this message in context:
http://www.nabble.com/Best-Practice-for-code-generation-scenarios-in-Maven-tp19638243p19638243.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]
Re: What's the point of listing all artifacts in archetype.xml?
Grzegorz Borkowski wrote: I wanted to create my own archetype... I've prepared set of prototype sources which should be used as tempate for creating new project. According to document Guide to creating archetypes I should put them under src/main/resources/archetype-resources/. That's ok, I put them there. But then the user guide says that I have to put every prototype file name (with full path) into archetype.xml file! What for? (I gave up at this point, it is too much unnecessary work.) Try generating the archetype by running mvn archetype:create-from-project from the root of your prototype project. The generated archetype will be in target/generated-sources/archetype/. You will probably have to fine tune a little bit, but at least it saves you writing the file list in archetype.xml. What's the point of such data redundancy? If I have the complete file structure under src/main/resources/archetype-resources/, then maven archetype plugin should simply copy it when creating project from archetype. Putting the list of those files in archetype.xml is waste of time. Can somebody explain me why it was designed so? I can't answer that question I'm afraid -- to me the file list in archetype.xml seems redundant as well... Niels - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best Practice for code generation scenarios in Maven
--- On Tue, 9/23/08, stug23 wrote: Does anyone on this group do this differently than what I sketched out here? If so, why and what are the advantages of your alternative approach? I'm currently generating source into various /target/generated-sources sub-directories and using the build-helper plugin to add source trees. The module contains sub-classes of the generated classes and (famous last words) we don't have any reason to provide the base classes as their own artifact. For now, anyway, keeping things together seemed better. The only real advantage, and it seems slim, is that of locality and cohesiveness. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best Practice for code generation scenarios in Maven
no you should generate into a new directory and add it as a source compile
root...
attach he plugin to generate-sources and it will be compiled and jar'd up just
like other code...
see the jaxb2 or xmlbeans plugins for examples...
On Wed, 24 Sep 2008 10:16:48 stug23 wrote:
I am currently porting an Ant-powered code generator to Maven and would
like to get input from this group for best practices with respect to code
generation in Maven.
Let's see if I have this right:
I wrote a Maven mojo to drive the code generator and can configure it in
the Maven project used for code generation.
I should always isolate the code generation into a single Maven module
(this could be part of a multi-module Maven project though) so that I can
declare the source directory for the generated code under the target
directory.
For example, something like this would be declared in the module where code
generation takes place:
build
sourceDirectory${project.build.directory}/codegen/java/sourceDirectory
...
...
The jar file artifact resulting from the code generation module would only
contain class files from the generator.
Since the standard src/main/java sourceDirectory/ has been 'usurped' by
the source directory where the code generator wrote its code, I shouldn't
have any other Java code under src/main/java.
Does this sound correct? Is this the best practice for a Maven module for
code generation? Does anyone on this group do this differently than what I
sketched out here? If so, why and what are the advantages of your
alternative approach?
Thanks in advance for your input!
:handshake:
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Purpose and Status of 'stage' Plugin
I didn't see it on the mojo site listed under Sandbox plugins http://mojo.codehaus.org/plugins.html Should it be added? Site/docs aren't to be had, or so I'm assuming. I did find an entry in the snapshot repo at http://snapshots.repository.codehaus.org/org/codehaus/mojo/wagon-maven-p lugin/ Thanks, I'll see if I can't build from source locally. Brad -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 4:45 PM To: Maven Users List Subject: Re: Purpose and Status of 'stage' Plugin [EMAIL PROTECTED] also has a maven-wagon-plugin currently in the sandbox. Give it a try and feedback On Tue, Sep 23, 2008 at 2:43 PM, Dan Tran [EMAIL PROTECTED] wrote: there already a JIRA for that. On Tue, Sep 23, 2008 at 2:34 PM, Harper, Brad [EMAIL PROTECTED] wrote: So it sounds like your 'staging' repo is for a semi-formal QA process, like what we call User Acceptance Test [UAT] and the plugin is used to promote the entire repository to a final/production repo. But you promote the entire repo -- wouldn't it be better to have the ability to promote at a finer-grained level? I.e. at the artifact level? I'm looking to fit the maven repo deployment/release model into a scheme where Apache continuum builds run nightly and resulting artifacts are deployed to a specific QA repository. Certain WAR artifacts are suitable for testing and any arbitrary one may be deemed fit for UAT. It would be ideal to be able to promote an artifact [without having to rebuild it] and to redeploy it to a segregated repository. If approved in UAT, it could be promoted to production status [again without having to rebuild it]. QA and production folks would know that the artifact is *exactly* what had been built and qualified originally. Segregation is important, so we can demonstrate to auditors that a process attempts to prevent non-qualified apps from entering a production environment. Production staff can only pull artifacts from a specific repo and artifacts can enter that repo only under controlled conditions. I was hoping that the staging plugin could help somewhat in this by allowing us to move artifacts between repos. Brad -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 3:54 PM To: Maven Users List Subject: Re: Purpose and Status of 'stage' Plugin At my company, at release time ( ie after we beat the heck out of snapshot build), we cut a release, but deploy to a staging repo. Then more ppl will test it. if approve, we use stage plugin to move the entire staging repo to a officially one. if not approve, we yank the staging repo, do some fix and cut another release to staging. The process repeats until everyone likes it. Currently the stage plugin can only move source target thru http, to a target repo using scp. -D On Tue, Sep 23, 2008 at 1:47 PM, Wayne Fay [EMAIL PROTECTED] wrote: (As I understand it...) Before the Maven dev team pushes builds out to the general public, they get pushed to a staging repo where they can be fully tested. Once the tests are complete, the files need to be pushed from the staging repo to the real public repo. This plugin makes the process easier and reduces errors. You can probably find more info about this plugin in the Maven Dev list archives. Wayne On Tue, Sep 23, 2008 at 1:38 PM, Harper, Brad [EMAIL PROTECTED] wrote: Can anyone comment on the purpose [and status] of the 'stage' plugin? Apart from the statement Its main use is for copying artifacts from a staging repository to the real repository. at http://maven.apache.org/plugins/maven-stage-plugin/, there isn't much explanation. I don't find many references to it in posts, nor does it seem to be addressed by the upcoming Maven: A Definitive Guide and older Better Builds with Maven texts. Specifically, what is a 'staging repository' [vs. a 'real repository']? Would the plugin be used to move all artifacts from one repo to another, or does it move only specific artifacts/versions? From content at http://maven.apache.org/plugins/maven-stage-plugin/usage.html, the answer would appear to be the former ... but I don't see much utility in that use case. What am I missing? Thanks. Brad - 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] - To
Re: frustration with testNG tests running twice.
Yes, they reside in src/test/java What do you want me to comment out? I commented this out but they still ran in the unit test pahase: execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/ testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution On Tue, Sep 23, 2008 at 3:12 PM, Brett Porter [EMAIL PROTECTED]wrote: 2008/9/24 Mick Knutson [EMAIL PROTECTED]: What doe you mean *default location* ? Do you mean package names? src/test/java which would be picked up by default - do your tests reside in there? ie, if you comment out all the below and run mvn test, do they run? - Brett On Mon, Sep 22, 2008 at 7:59 PM, Brett Porter [EMAIL PROTECTED] wrote: They are probably in the default location so the default configuration runs them in the test phase. - Brett 2008/9/20 Mick Knutson [EMAIL PROTECTED]: I have this declaration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution execution idintegration-tests/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnoretrue/testFailureIgnore suiteXmlFiles suiteXmlFilesrc/test/resources/testng-functional.xml/suiteXmlFile /suiteXmlFiles groupssuite-init,database,functional,selenium/groups excludeGroupsunit/excludeGroups /configuration /execution /executions /plugin Now I even commented out the phasetest/phase to stop unit test from running, but they run anyways. And because there is not a testng.xml for that phase, the tests fail. Can someone please help me get just my functional tests to run in the phaseintegration-test/phase ??? Your help is greatly appreciated! -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com
Re: frustration with testNG tests running twice.
I'm a bit confused by your configuration. You have all your test sources in src/test/java and are excluding everything from unit testing, then running it all in integration-testing? IS the unit execution designed to run some unit tests, or disable the default ones? - Brett 2008/9/24 Mick Knutson [EMAIL PROTECTED]: Yes, they reside in src/test/java What do you want me to comment out? I commented this out but they still ran in the unit test pahase: execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/ testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution On Tue, Sep 23, 2008 at 3:12 PM, Brett Porter [EMAIL PROTECTED]wrote: 2008/9/24 Mick Knutson [EMAIL PROTECTED]: What doe you mean *default location* ? Do you mean package names? src/test/java which would be picked up by default - do your tests reside in there? ie, if you comment out all the below and run mvn test, do they run? - Brett On Mon, Sep 22, 2008 at 7:59 PM, Brett Porter [EMAIL PROTECTED] wrote: They are probably in the default location so the default configuration runs them in the test phase. - Brett 2008/9/20 Mick Knutson [EMAIL PROTECTED]: I have this declaration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution idunit-tests/id phasetest/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnorefalse/testFailureIgnore excludes exclude**/*.java/exclude /excludes /configuration /execution execution idintegration-tests/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip testFailureIgnoretrue/testFailureIgnore suiteXmlFiles suiteXmlFilesrc/test/resources/testng-functional.xml/suiteXmlFile /suiteXmlFiles groupssuite-init,database,functional,selenium/groups excludeGroupsunit/excludeGroups /configuration /execution /executions /plugin Now I even commented out the phasetest/phase to stop unit test from running, but they run anyways. And because there is not a testng.xml for that phase, the tests fail. Can someone please help me get just my functional tests to run in the phaseintegration-test/phase ??? Your help is greatly appreciated! -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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 Vacation Rental: http://tahoe.baselogic.com -- Brett Porter Blog: http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- Thank You… Mick Knutson BASE Logic, inc. (415) 354-4215 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:
[Fwd: verbosetrue/verbose is ignored for maven-compiler-plugin]
Has anyone experienced this problem? ---BeginMessage--- I don't see the effect of verbosetrue/verbose. When I run with -X, I do see that verbose = true, but I don't see it being passed to javac. I tried with fork = true and the command line that was used to invoke javac did not have verbose option set. I am using default compiler. Thanks, Sahoo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---End Message--- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using spring How to share jpa applicationContext.xml file with main src and test source?
I'm using the spring PetClinic as an example application to follow. I
have things building and working in maven2, but I'm having an issue
with the junit tests.
I'd like to be able to share one of my application-context.xml files
that is in my src/main/resources directory without having to keep it
in two places.
The application example I'm using for testing needs to call
AbstractJpaTests which requires one to override the getConfigPaths.
The problem is how do I get a handle outside of the test-classes in
which the tests are being run?
//the files below exist in my tests-classes directory, but I'd also
like to use the one in my standard classes directory as well.
// the / slash only seems to bring me to the base of my test-classes directory
@Override
protected String[] getConfigPaths() {
return new String[] {
/applicationContext-jpa.xml,
/applicationContext-entityManager.xml
};
}
}
I've even tried adding an extra entry in my pom.xml for to use the
main resources as well but it didn't seem to help:
testResources
testResource
directorysrc/main/resources/directory
includes
include**/*.xml/include
/includes
/testResource
testResource
directorysrc/test/resources/directory
includes
include**/*.xml/include
/includes
/testResource
/testResources
--
Rick
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: frustration with testNG tests running twice.
Are you setting the testName attribute at all in any of your test classes? I noticed an interesting bug this morning with surefire/testng where if I had tests changing the testName, then the testng XML file was generated all wonky (ignoring groups, adding all classes) and causing all manner of weird things running. I´ve not yet submitted this to jira, but thats coming soon.. On Wed, Sep 24, 2008 at 5:10 AM, Mick Knutson [EMAIL PROTECTED]wrote: What doe you mean *default location* ? Do you mean package names?
