[M2] Support for non-java sources ?
In Maven 2 POM documentation, it seems that I will only be able to create Java project with Maven. sourceDirectory/ scriptSourceDirectory/ testSourceDirectory/ sourceDirectory points by default to src/main/java. Does it mean that if I want to create non-java project I can't indicate sources in the pom ? Or does it mean that I can declare a new artifact type in maven (let's say for C++ stuffs), place the c++ sources in the POM sourceDirectory, and have my C++ files compiled as part of the normal maven life cycle ? What happen if the source type can't be guessed from the artifact type (I think DLL can be created in more than one language, same I guess a maven plugin can be Java or Marmelade or ...). And if I need to mix different languages in my sources, I'll do : src/main/lang1, src/main/lang2, ... but how will the compile tasks do the right thing ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Too many things in the POM ?
I have the feeling the POM will carry too many things. After all, POM is in SCM, so it is versionned, it is source related, it can't provide deployment infos, or development platform context, which can change after the release has been done. At the first reading of the POM documentation, I see : reposiroty : Remote Repository. (I guess the one where the packaged artifact will be deployed) Does it mean that my project sources must know where my remote repository is installed ? What happen if my company change computer names (for example she got bought by another company who already have a maven repository and we want merge them) ? This problem was already an issue in Maven 1 too, and still is on those : issue management, site:deploy target, etc. I have slightly the same conceptual difficulties with some site reports. For me there are different kind of reports. Some I want to execute during Continuous integration (on SNAPSHOT) and some I want to execute on stable releases (versions). Some reports can be attached to both : javadoc, tests, xref, faq, install guide, user guide, pmd, findbugs, checkstyle, ... they apply to ONE configuration. Some reports are NOT version related, they apply to the whole configuration management : last 30 days changelogs, Developper activity, ... If the changelog was : every change log since last version, it would become a configuration report and I would be ok with it, but the fact it will deal with a period of time based on when I run it, breaks this (I should be able to check out a specific VERSION, whenever I want, even years ahead in the future, generate the site and obtain the exact same result than when i did the first time). I have the feeling Maven doesn't clearly separated between a configuration and the whole project lifespan. For me there should be a tool for configuration-based tasks, and a tool for project-based tasks. A versionned POM, that follow the configuration lifecycle, and some other project-settings separated from the POM. I think this second item should be handled by CruiseControl-like tools, and could integrate other tools that track the project evolution like some code review tools with history (e.g. Hammurapi). Or ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] Too many things in the POM ?
Hi Haryon, I think you make some very valid points. ATM, Maven has mostly focused on instant reports and generating instant view of projects. We now need to integrate history and I know for sure that the m2 team has started working on this. I don't know what the solution will be though. When you start working on history you need rapidly to link reports to versions so I'm sure this use case will be taken into account somehow. I'm also curious to see what architecture will be put in place to solve this need. Thanks -Vincent -Original Message- From: Haryon [mailto:[EMAIL PROTECTED] Sent: lundi 11 avril 2005 11:13 To: Maven List Subject: [M2] Too many things in the POM ? I have the feeling the POM will carry too many things. After all, POM is in SCM, so it is versionned, it is source related, it can't provide deployment infos, or development platform context, which can change after the release has been done. At the first reading of the POM documentation, I see : reposiroty : Remote Repository. (I guess the one where the packaged artifact will be deployed) Does it mean that my project sources must know where my remote repository is installed ? What happen if my company change computer names (for example she got bought by another company who already have a maven repository and we want merge them) ? This problem was already an issue in Maven 1 too, and still is on those : issue management, site:deploy target, etc. I have slightly the same conceptual difficulties with some site reports. For me there are different kind of reports. Some I want to execute during Continuous integration (on SNAPSHOT) and some I want to execute on stable releases (versions). Some reports can be attached to both : javadoc, tests, xref, faq, install guide, user guide, pmd, findbugs, checkstyle, ... they apply to ONE configuration. Some reports are NOT version related, they apply to the whole configuration management : last 30 days changelogs, Developper activity, ... If the changelog was : every change log since last version, it would become a configuration report and I would be ok with it, but the fact it will deal with a period of time based on when I run it, breaks this (I should be able to check out a specific VERSION, whenever I want, even years ahead in the future, generate the site and obtain the exact same result than when i did the first time). I have the feeling Maven doesn't clearly separated between a configuration and the whole project lifespan. For me there should be a tool for configuration-based tasks, and a tool for project-based tasks. A versionned POM, that follow the configuration lifecycle, and some other project-settings separated from the POM. I think this second item should be handled by CruiseControl-like tools, and could integrate other tools that track the project evolution like some code review tools with history (e.g. Hammurapi). Or ? - 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: a practical multiproject build
I have exactly the smae problem, can anybody who knows how to solve this problem reply? thanks, Bahaa On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE [EMAIL PROTECTED] wrote: I've been working with multiproject for a couple of days, so while I'm not exactly an expert, I feel reasonably confident with the following questions. Basically, I'd like to end up with 1 step to deploying only changes to a web application. Here's my directory structure: /project /application project.xml ... /webClient project.xml ... project.xml ... As I understand it, I need to run multiproject:something from the /project directory, to build the multiproject. Then, I'd like to run jboss:deploy-exploded-warfile from the /webClient directory. How can I bundle all of this into one goal within /project/maven.xml? Something like: The other thing I'm wondering is how manage the dependencies as SNAPSHOTs. For instance, since /webClient depends on /application, I'm guessing that I should have something like this in /webClient/project.xml: dependency groupIdproject/groupId artifactIdapplication/artifactId versionSNAPSHOT/version typejar/type properties war.bundletrue/war.bundle /properties /dependency And in /application/project.xml: currentVersionSNAPSHOT/currentVersion Additionally, /webClient/project.xml has: currentVersionSNAPSHOT/currentVersion Then, when I cut a release, I would replace SNAPSHOT with whatever version I'm releasing. Since I'll be actively developing both modules at once, they should be SNAPSHOTs right? Currently, I'm having difficulty getting multiproject to handle SNAPSHOT dependencies. It always tries to get the dependency from the remote repository despite the fact that the project SNAPSHOT is part of the multiproject. Does this make sense? Thanks, Dave - 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: a practical multiproject build
Hello,
You can filter the subprojects on which you want to call a goal by
adding the following on the root maven.xml :
goal name=myGoal
maven:reactor
basedir=${basedir}
includes=*/project.xml
postProcessing=false
goals=myGoal
ignoreFailures=false /
/goal
For your example, you should have :
goal name=jboss:deploy-exploded-warfile
maven:reactor
basedir=${basedir}
includes=webClient/project.xml
postProcessing=false
goals=myGoal
ignoreFailures=false /
/goal
In your case the subprojects should have the same version number. So I
think that you can set the version (SNAPSHOT) on the root POM
(project.xml) and remove it from subprojects. I hope it will resolve
your problem...
Simon
For the problem
On Apr 11, 2005 12:10 PM, Bahaa Nasrallah [EMAIL PROTECTED] wrote:
I have exactly the smae problem, can anybody who knows how to solve
this problem reply?
thanks,
Bahaa
On Apr 8, 2005 8:17 PM, Durham David R Jr Contr 805 CSPTS/SCE
[EMAIL PROTECTED] wrote:
I've been working with multiproject for a couple of days, so while I'm
not exactly an expert, I feel reasonably confident with the following
questions.
Basically, I'd like to end up with 1 step to deploying only changes to a
web application. Here's my directory structure:
/project
/application
project.xml
...
/webClient
project.xml
...
project.xml
...
As I understand it, I need to run multiproject:something from the
/project directory, to build the multiproject. Then, I'd like to run
jboss:deploy-exploded-warfile from the /webClient directory. How can I
bundle all of this into one goal within /project/maven.xml? Something
like:
The other thing I'm wondering is how manage the dependencies as
SNAPSHOTs. For instance, since /webClient depends on /application, I'm
guessing that I should have something like this in
/webClient/project.xml:
dependency
groupIdproject/groupId
artifactIdapplication/artifactId
versionSNAPSHOT/version
typejar/type
properties
war.bundletrue/war.bundle
/properties
/dependency
And in /application/project.xml:
currentVersionSNAPSHOT/currentVersion
Additionally, /webClient/project.xml has:
currentVersionSNAPSHOT/currentVersion
Then, when I cut a release, I would replace SNAPSHOT with whatever
version I'm releasing.
Since I'll be actively developing both modules at once, they should be
SNAPSHOTs right? Currently, I'm having difficulty getting multiproject
to handle SNAPSHOT dependencies. It always tries to get the dependency
from the remote repository despite the fact that the project SNAPSHOT is
part of the multiproject.
Does this make sense?
Thanks,
Dave
-
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]
--
Simon BRANDHOF
Hortis - La rencontre de l'Agilité et de l'Open-source
www.xp-suisse.org
www.hortis.ch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Proxy settings and different remote repos
Hello, I want to use two different repositories: a company-wide repository, and in second place to fall through to ibiblio if I can't find an artifact in the company repository. The problem comes in when I have to specify my proxy settings: to access my company repo, I don't need to specify my proxy settings, but to access ibiblio, that's mandatory. So the question is: is there a solution to that dilema? How can I specify two remote repositories requiring different proxy settings (or no settings at all to be clear)? Does Maven provide some magic parameters for that? Thanks in advance, -- Guillaume Laforge http://glaforge.free.fr/weblog/?catid=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proxy settings and different remote repos
Unfortunately no. Maven 1.1 does accept proxy exclusions, but not 1.0.2. You can see if httpclient will pick them up via the standard java system property: -Dproxy.nonProxyHosts=*.mycompany.com Another alternative is to set up maven-proxy on your company repo - all your clients can connect to that, and it will fallback to ibiblio when not saved locally. - Brett On Apr 11, 2005 9:42 PM, Guillaume Laforge [EMAIL PROTECTED] wrote: Hello, I want to use two different repositories: a company-wide repository, and in second place to fall through to ibiblio if I can't find an artifact in the company repository. The problem comes in when I have to specify my proxy settings: to access my company repo, I don't need to specify my proxy settings, but to access ibiblio, that's mandatory. So the question is: is there a solution to that dilema? How can I specify two remote repositories requiring different proxy settings (or no settings at all to be clear)? Does Maven provide some magic parameters for that? Thanks in advance, -- Guillaume Laforge http://glaforge.free.fr/weblog/?catid=2 - 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]
M2 with Java5
Hi there, Just trying out the alpha release of M2 was wondering if there's any issues with compiling Java5? It doesn't seem to like the new syntax - is there a property I need to set to anywhere? Aside from that it's looking great at the moment - keep up the good work! BTW, is this the correct mailing list for M2? I did read some discussion about merging M1 M2 mailing lists back together, so I assumed so. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Too many things in the POM ?
On Apr 11, 2005 7:13 PM, Haryon [EMAIL PROTECTED] wrote: I have the feeling the POM will carry too many things. After all, POM is in SCM, so it is versionned, it is source related, it can't provide deployment infos, or development platform context, which can change after the release has been done. We took things out for this reason (the list of previous versions, for example). Nothing in the POM should be different depending on contexts - the only difference is the distributionManagement and siteManagement which should have multiples but don't. There is already a JIRA issue to completely setup server profiles so that the amount in the POM is minimal - it should just select which servers to use. Likewise, the list of developers should just be keyed to a database housed elsewhere. per-user type things are all in settings.xml at the moment - eg repository usernames, passwords and keys. Does it mean that my project sources must know where my remote repository is installed ? What happen if my company change computer names (for example she got bought by another company who already have a maven repository and we want merge them) ? You can inherit to as many levels as you like. When m2 better supports it, recommended policy would be to have a company wide POM that defines your shared settings. Then, each department might inherit from that and customise bits, and so on down to the individual project and model. The problem with this at the moment is that you must name them all SNAPSHOT or it won't work (you'd need to change the name of everything whenever a new one was published!) We're working on improving that mechanism. (I should be able to check out a specific VERSION, whenever I want, even years ahead in the future, generate the site and obtain the exact same result than when i did the first time). This is just a matter of those plugins supporting that, and should be straightforward. We haven't implemented many reports for m2 yet. As Vincent mentioned, we are working on this, and intend to provide reports that will also run dynamically (so changelog is always up to date), or once off (for a release). Does this address all of your concerns? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Support for non-java sources ?
For anything where the type is not enough to figure it out, you would add plugin configuration. eg, when there is an aspectj plugin, you'll probably use this instead of aspectSourceDirectory/: plugin artifactIdmaven-aspectj-plugin/artifactId configuration aspectSourceDirectorysrc/main/aspects/aspectSourceDirectory /configuration /plugin This is actually more scalable to allowing other languages, and we fully intend to support native languages and more at some point. - Brett On Apr 11, 2005 6:54 PM, Haryon [EMAIL PROTECTED] wrote: In Maven 2 POM documentation, it seems that I will only be able to create Java project with Maven. sourceDirectory/ scriptSourceDirectory/ testSourceDirectory/ sourceDirectory points by default to src/main/java. Does it mean that if I want to create non-java project I can't indicate sources in the pom ? Or does it mean that I can declare a new artifact type in maven (let's say for C++ stuffs), place the c++ sources in the POM sourceDirectory, and have my C++ files compiled as part of the normal maven life cycle ? What happen if the source type can't be guessed from the artifact type (I think DLL can be created in more than one language, same I guess a maven plugin can be Java or Marmelade or ...). And if I need to mix different languages in my sources, I'll do : src/main/lang1, src/main/lang2, ... but how will the compile tasks do the right thing ? - 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 2
Thanks. It worked for me. My case is simple though: I created an empty project, made it eclipse project using your plugin, and then imported it into eclipse. -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 6:31 PM To: Maven Users List Subject: Re: Maven 2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just letting you know that the maven-eclipse-plugin for Maven 2.0 is deployed to ibiblio.org. To use it, type: m2 eclipse:eclipse in the root of your project directory. HTH, john Ilyevsky, Leonid (Equity Trading) wrote: I got maven2 today, and I am eager to start. Two main problems right in the beginning: 1. Where do I specify my web proxy ? Obviously maven2 does not use build.properties anymore. 2. On maven2 webpage they suggest to consult documentation frequently. Where is documentation anyway? I couldn't find it. If I looked at documentation, I probably wouldn't have the problem #1. Please help. I cannot do anything without proxy settings. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCVwYuK3h2CZwO/4URAnyOAJ4w40v43ay9MQOPPWh/y9qDCGgscQCfaNIK lYeMHqoeTGoAYu3xUnmbSLQ= =m1lp -END PGP SIGNATURE- - 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: reactor
You must define the maven namespace into the root node of maven.xml : project xmlns:maven=jelly:maven Cheers, Simon http://www.xp-swiss.org On Apr 11, 2005 4:20 PM, Bahaa Nasrallah [EMAIL PROTECTED] wrote: hi, in my maven.xml i have goal name=buildAll maven:reactor includes=**/project.xml excludes= banner=Building goals=Complete ignoreFailures=false/ /goal in the command line i try to run maven buildAll and i get : Fatal Error [line 73, row 33]: The prefix maven for element maven:reactor is not bound. what's wrong? Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon BRANDHOF Hortis - La rencontre de l'Agilité et de l'Open-source www.xp-suisse.org www.hortis.ch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: reactor
project xmlns:maven=jelly:maven ... is required at the top. On Apr 12, 2005 12:20 AM, Bahaa Nasrallah [EMAIL PROTECTED] wrote: hi, in my maven.xml i have goal name=buildAll maven:reactor includes=**/project.xml excludes= banner=Building goals=Complete ignoreFailures=false/ /goal in the command line i try to run maven buildAll and i get : Fatal Error [line 73, row 33]: The prefix maven for element maven:reactor is not bound. what's wrong? Thanks in advance - 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]
[M2] plugins language?
Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. Thanks Yuriy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] plugins language?
Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] plugins language?
While marmalade is our preferred option for those wanting to port m1 plugins or use ant tasks, java and beanshell will be the preferred options otherwise. Beanshell support is scheduled for alpha-2. /me goes to write a FAQ entry. Cheers, Brett On Apr 12, 2005 1:25 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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]
[M2] 'Getting Started' guide fails in current state
Hello, If you work through the current 'Getting Started' page for Maven 2, the last step (multiple modules) fails at the install goal. This is because a WAR with a non-default name cannot be installed in the repository. 1. The example given to create a WAR uses a 'plugins' element in the pom.xml. This creates a war file with the short name my-webapp.war. 2. This war file cannot be installed in the repository. The 'install' goal fails as it looks for the fully-qualified artifact name (including version string) in the target directory. Fix: if you remove the plugins element from the webapp pom.xml, the app builds and installs correctly. Question: Is there some parameter I can use to install a WAR with a non-default name? Thanks - Aaron =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Aaron Bell Principal Consultant Clockwork Logic Ltd. 1/8 Sunbury Place, Dean Village EDINBURGH, EH4 3BY m. +44 (0)7900 423577 t/f. +44 (0)131 226 6575 w. http://clockworklogic.co.uk =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] 'Getting Started' guide fails in current state
On Apr 12, 2005 1:31 AM, Aaron Bell [EMAIL PROTECTED] wrote: Hello, If you work through the current 'Getting Started' page for Maven 2, the last step (multiple modules) fails at the install goal. This is because a WAR with a non-default name cannot be installed in the repository. Good catch. Actually, you missed the step that had already removed it during the tutorial :) Question: Is there some parameter I can use to install a WAR with a non-default name? No, this is not the intention of the repository (see the mail archives for a greater explanation). Thanks, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] plugins language?
Hi Brett, I think Jason van Zyl wrote he would touch Groovy not even with a polestick Is there any Groovy support planned? I use Beanshell and Groovy but Groovy is much more powerful in doing things quickly while Beanshell is easier to grasp Cheers, Siegfried Goeschl Brett Porter wrote: While marmalade is our preferred option for those wanting to port m1 plugins or use ant tasks, java and beanshell will be the preferred options otherwise. Beanshell support is scheduled for alpha-2. /me goes to write a FAQ entry. Cheers, Brett On Apr 12, 2005 1:25 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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: [M2] plugins language?
We will allow the use of Groovy - and virtually any other scripting language someone can commit a small amount of time to implementing a factory for, if there is demand. We would recommend waiting for Groovy to have a 1.0 release so the API (and language!) is stable. What we will not be doing is actively supporting it (in terms of answering questions about how to use it) like we currently do for Jelly in Maven 1.x. Beanshell is more mature, and we want a language that users will find answers for when they look, and that when they find bugs, it is clearly defined where they actually are. Hope this helps... - Brett On Apr 12, 2005 1:43 AM, Siegfried Goeschl [EMAIL PROTECTED] wrote: Hi Brett, I think Jason van Zyl wrote he would touch Groovy not even with a polestick Is there any Groovy support planned? I use Beanshell and Groovy but Groovy is much more powerful in doing things quickly while Beanshell is easier to grasp Cheers, Siegfried Goeschl Brett Porter wrote: While marmalade is our preferred option for those wanting to port m1 plugins or use ant tasks, java and beanshell will be the preferred options otherwise. Beanshell support is scheduled for alpha-2. /me goes to write a FAQ entry. Cheers, Brett On Apr 12, 2005 1:25 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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]
Generate manifest classpath entry?
Hi, is it possible to generate a Class-Path entry in the generated manifest file that includes all dependend jars? See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Main%20Attributes for more info regards, Wim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] plugins language?
but What lang will be used for core plugins? - Original Message - From: Emmanuel Venisse [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Monday, April 11, 2005 6:25 PM Subject: Re: [M2] plugins language? Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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 2.0 Technology Preview release
Please, don't cross-post to multiple lists. http://maven.apache.org/maven2/maven1.html#m1-future http://maven.apache.org/maven2/about.html#release-schedule (there is currently an August target for 2.0 final) - Brett On Apr 12, 2005 1:58 AM, David Jackman [EMAIL PROTECTED] wrote: Some docs on the Maven site talk about version 1.1. Is an interim 1.1 release still planned, or is everything looking forward to 2.0? Is there a projected release date for 2.0 at this time? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 10:36 AM To: Maven Users List Cc: Maven Developers List; Maven 2 Developers List Subject: Maven 2.0 Technology Preview release The first Maven 2.0 Technology Preview release is now out. http://maven.apache.org/maven2/index.html We're looking forward to hearing your feedback, ideas, and (to a lesser extent :) bug reports. If you need help with the release, please consult the documentation frequently as we continue to update it, and subscribe to the users@maven.apache.org mailing list. For more information, please see http://maven.apache.org/maven2/about.html#get-help We welcome contributors to the Maven project - if you are interested in helping out, please see http://maven.apache.org/maven2/about.html#get-involved Thanks to everyone who has worked on this release! -- The Apache Maven Team - 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: Maven 2.0 Technology Preview release
Some docs on the Maven site talk about version 1.1. Is an interim 1.1 release still planned, or is everything looking forward to 2.0? Is there a projected release date for 2.0 at this time? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 10:36 AM To: Maven Users List Cc: Maven Developers List; Maven 2 Developers List Subject: Maven 2.0 Technology Preview release The first Maven 2.0 Technology Preview release is now out. http://maven.apache.org/maven2/index.html We're looking forward to hearing your feedback, ideas, and (to a lesser extent :) bug reports. If you need help with the release, please consult the documentation frequently as we continue to update it, and subscribe to the users@maven.apache.org mailing list. For more information, please see http://maven.apache.org/maven2/about.html#get-help We welcome contributors to the Maven project - if you are interested in helping out, please see http://maven.apache.org/maven2/about.html#get-involved Thanks to everyone who has worked on this release! -- The Apache Maven Team - 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: [M2] plugins language?
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: lundi 11 avril 2005 17:53 To: Maven Users List; [EMAIL PROTECTED] Subject: Re: [M2] plugins language? We will allow the use of Groovy - and virtually any other scripting language someone can commit a small amount of time to implementing a factory for, if there is demand. Will that factory need to be included in the Maven code or could it sit, say, in the groovy code itself and M2 be easily configured to use it? I believe it's a plexus component and it needs to be registered in plexus. Will m2 users be able to change the plexus configuration files? In other words, could it be maintained outside of Maven? [snip] Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] plugins language?
My next build problem, see below. The commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom indeed is not there. [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 install [INFO] [INFO] Building null [INFO] [INFO] [resources:resources] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Unable to resolve required dependencies for goal at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(Default LifecycleExecutor.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transitively resolving artifacts: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:191) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:723) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:355) ... 14 more Caused by: org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException : Error retrieving metadata [commons-logging:commons-lo gging:jar:1.0.4] : at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:307) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:187) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:89) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:303) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find artifact: commons-logging:commons-logging:pom:1.0.4 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:167) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:149) at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:83) ... 18 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 12:04:37 EDT 2005 [INFO] Final Memory: 1M/63M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] plugins language?
Will that factory need to be included in the Maven code or could it sit, say, in the groovy code itself and M2 be easily configured to use it? I believe it's a plexus component and it needs to be registered in plexus. Yes, it could be in groovy, or a groovy library. There is already an example in plexus-component-factories. Will m2 users be able to change the plexus configuration files? In alpha-1, it must be in plexus.xml inside the maven-core JAR. Once a correction is made to the plexus container, it can be defined in the groovy JAR, and you'd simply need to drop it into maven2/lib (it may even be possible to load it on demand - I'm not entirely sure). In other words, could it be maintained outside of Maven? Absolutely. There is another aspect to it - parsing the goal and parameter definitions out of the script. Marmalade (XML) and Java (QDOX) both define it inside the source file. We could have a generic external descriptor includer so this would be optional - but it is handy to be able to extract it from the source files. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Another build problem
My next build problem, see below. It is looking for commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom And it is not there. [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 install [INFO] [INFO] Building null [INFO] [INFO] [resources:resources] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Unable to resolve required dependencies for goal at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(Default LifecycleExecutor.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transitively resolving artifacts: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:191) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:723) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:355) ... 14 more Caused by: org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException : Error retrieving metadata [commons-logging:commons-lo gging:jar:1.0.4] : at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:307) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:187) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:89) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:303) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find artifact: commons-logging:commons-logging:pom:1.0.4 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:167) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:149) at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:83) ... 18 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 12:04:37 EDT 2005 [INFO] Final Memory: 1M/63M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: 'maven.repo.local' not honored by all
Anyone??? On Apr 8, 2005 3:12 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: In my project.properties file, I set maven.repo.local=C:\blah\repository. I then proceeded to blow away %HOMEDRIVE%%HOMEPATH%\.maven\repository. Then I ran maven java:compile. I see where it downloads my project;s dependencies, and it places them in the appropriate local repository location. However, it also downloads commons-lang, antlr commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug? -- Jamie -- Jamie Bisotti Software Engineer Lexmark International, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generate manifest classpath entry?
Yes it is Take a look at the jar plugin properties: http://maven.apache.org/reference/plugins/jar/properties.html In short, you must set the property: maven.jar.manifest.classpath.add=true And in your project.xml, in each dependency, add the following property: properties jar.manifest.classpathtrue/jar.manifest.classpath /properties That should do the trick. Hope it helps. Eric. Wim Deblauwe wrote: Hi, is it possible to generate a Class-Path entry in the generated manifest file that includes all dependend jars? See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Main%20Attributes for more info regards, Wim - 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: Another build problem
It is probably because this file: http://www.ibiblio.org/maven/commons-logging/poms/commons-logging-1.0.4.pom was published with the wrong version, so the conversion tool was unable to convert. I have corrected it, and hopefully within 4 hours it will have propogated to ibiblio. You should report the problem to commons-dev@jakarta.apache.org - I will do this now. commons-logging-1.0.3 works... - Brett On Apr 12, 2005 2:14 AM, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote: My next build problem, see below. It is looking for commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom And it is not there. [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 install [INFO] [INFO] Building null [INFO] [INFO] [resources:resources] Downloading: commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2 [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Unable to resolve required dependencies for goal at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:375) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executePhase(Default LifecycleExecutor.java:417) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:140) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transitively resolving artifacts: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:191) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependenci es(DefaultPluginManager.java:723) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:355) ... 14 more Caused by: org.apache.maven.artifact.resolver.TransitiveArtifactResolutionException : Error retrieving metadata [commons-logging:commons-lo gging:jar:1.0.4] : at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:307) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransi tively(DefaultArtifactResolver.java:187) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:89) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.collect(Defau ltArtifactResolver.java:303) ... 17 more Caused by: org.apache.maven.project.ProjectBuildingException: Unable to find artifact: commons-logging:commons-logging:pom:1.0.4 at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:167) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:149) at org.apache.maven.artifact.MavenMetadataSource.retrieve(MavenMetadataSour ce.java:83) ... 18 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 12:04:37 EDT 2005 [INFO] Final Memory: 1M/63M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here
Re: 'maven.repo.local' not honored by all
This should work, and I've never seen this happen. Please file it in JIRA for further investigation. - Brett On Apr 12, 2005 2:16 AM, Jamie Bisotti [EMAIL PROTECTED] wrote: Anyone??? On Apr 8, 2005 3:12 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: In my project.properties file, I set maven.repo.local=C:\blah\repository. I then proceeded to blow away %HOMEDRIVE%%HOMEPATH%\.maven\repository. Then I ran maven java:compile. I see where it downloads my project;s dependencies, and it places them in the appropriate local repository location. However, it also downloads commons-lang, antlr commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug? -- Jamie -- Jamie Bisotti Software Engineer Lexmark International, Inc. - 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]
REPOST: variable expansion in xdoc's?
I'm reposting this because it seems very basic but have not yet seen a way to do this. I hope someone has a solution. Thanks, Mike --- Mike Traum [EMAIL PROTECTED] wrote: I'm trying to obtain some of my pom variables in my user xdocs. I've been looking through all of the xdoc code and I can't see how this is done. I'm assumming it has something to do with the jsl, but I can't figure out how to apply a context to jsl:applyTemplates. The documentation for commons-jelly-tags-jsl is quite sparse. Thanks, Mike __ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependencies' Licenses list
Hello, Is there a plugin for listing all the licenses used by a maven project dependencies (and all their dependencies recursively)? I could not find anything like that among the listed plugins.. Does anybody know anything about it? What I'd like to do is, for instance, to have dependencies.html to show an extra column with the license that applies for that row's dependency, maybe with the license type and a link to real license.. That way I could go through the list and check all I'd need to accept in order to use the my project's lib. Thanks, Diego -- Diego Ballve Digital Artefacts Europe http://www.digital-artefacts.fi/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependencies' Licenses list
Nothing at present, though we have thought of doing some work in this area. Theoretically, you should not have to drill down because the libraries should be license in such a way that that is all you have to accept, but it can get complicated. (eg, if foo uses bar and bar is GPL, foo has to be GPL anyway - though this might not be the case if bar were LGPL, or if foo didn't import any code from bar) - Brett On Apr 12, 2005 2:52 AM, Diego Ballve [EMAIL PROTECTED] wrote: Hello, Is there a plugin for listing all the licenses used by a maven project dependencies (and all their dependencies recursively)? I could not find anything like that among the listed plugins.. Does anybody know anything about it? What I'd like to do is, for instance, to have dependencies.html to show an extra column with the license that applies for that row's dependency, maybe with the license type and a link to real license.. That way I could go through the list and check all I'd need to accept in order to use the my project's lib. Thanks, Diego -- Diego Ballve Digital Artefacts Europe http://www.digital-artefacts.fi/ - 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: REPOST: variable expansion in xdoc's?
Eric Giguere wrote: Hello This link was posted releated to variable values in the navigation.xml. Maybe this will also work in other xdoc documents..? Check it out: http://cvs.apache.org/viewcvs.cgi/maven-plugins/pdf/src/plugin-test/xdocs/navigation.xml?rev=1.2view=markup Hope it helps Eric. No. Navigation.html is special and is a Velocity template. User provided xdocs are normal XML elements without any expansion. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: a practical multiproject build
You can filter the subprojects on which you want to call a goal by
adding the following on the root maven.xml :
goal name=myGoal
maven:reactor
basedir=${basedir}
includes=*/project.xml
postProcessing=false
goals=myGoal
ignoreFailures=false /
/goal
Yeah, I can do this by manipulating the maven.multiproject.excludes and
maven.multiproject.includes properties.
In your case the subprojects should have the same version number. So
I think that you can set the version (SNAPSHOT) on the root POM
(project.xml) and remove it from subprojects. I hope it will
resolve your problem...
Right, part of my problem is that I don't understand exactly how the
SNAPSHOT stuff works. Perhaps SNAPSHOTs don't make as much sense in a
multiproject context at least as far the modules are concerned. I
replaced SNAPSHOT with an actual version number within the different
modules' project.xml files and the build works smoothly now.
Thanks,
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependencies' Licenses list
Thanks Brett, Yes, libreries should respect dependency libraries' licenses, but since whoever distributes them at last is the one to blame, I need to be sure they are ok. The compiled list would help that task, now performed lib by lib. GPL is one of the cases - and a description would be needed to say the level of dependency.. it can get tricky, I know. Another is the non-distributable, devel/testing -only as some Sun libraries in JWSDP are. You could even use them to compile your code / OS code, but you could not redistribute them. I've experienced something like that. Btw, I've started writing an ant script that creates a local repository from installed JWSDP 1.5, I'm changing a project that depends on them to use Maven. I wonder if that would be of any use for the community. I can upload it somewhere and send a link to this list when it's ready. Regards Diego Brett Porter wrote: Nothing at present, though we have thought of doing some work in this area. Theoretically, you should not have to drill down because the libraries should be license in such a way that that is all you have to accept, but it can get complicated. (eg, if foo uses bar and bar is GPL, foo has to be GPL anyway - though this might not be the case if bar were LGPL, or if foo didn't import any code from bar) - Brett On Apr 12, 2005 2:52 AM, Diego Ballve [EMAIL PROTECTED] wrote: Hello, Is there a plugin for listing all the licenses used by a maven project dependencies (and all their dependencies recursively)? I could not find anything like that among the listed plugins.. Does anybody know anything about it? What I'd like to do is, for instance, to have dependencies.html to show an extra column with the license that applies for that row's dependency, maybe with the license type and a link to real license.. That way I could go through the list and check all I'd need to accept in order to use the my project's lib. Thanks, Diego - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 'maven.repo.local' not honored by all
If its useful I've got the same thing happening on OSX.. I symlink to a setup script that sets the varibles as I like them and its not digging.. #maven setup script. export M2_HOME=/Developer/Java/Maven2 export PATH=$M2_HOME/bin:$PATH export JAVA_HOME=/Library/Java/Home export M2_HOME_LOCAL=~/Library/Maven2 m2 -Dmaven.repo.local=$M2_HOME_LOCAL $@ Works fine with maven 1.0.. I'll have a dig through the sources and see if there are anychanges to the variable names. Mark On Apr 11, 2005 6:34 PM, Brett Porter [EMAIL PROTECTED] wrote: This should work, and I've never seen this happen. Please file it in JIRA for further investigation. - Brett On Apr 12, 2005 2:16 AM, Jamie Bisotti [EMAIL PROTECTED] wrote: Anyone??? On Apr 8, 2005 3:12 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: In my project.properties file, I set maven.repo.local=C:\blah\repository. I then proceeded to blow away %HOMEDRIVE%%HOMEPATH%\.maven\repository. Then I ran maven java:compile. I see where it downloads my project;s dependencies, and it places them in the appropriate local repository location. However, it also downloads commons-lang, antlr commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug? -- Jamie -- Jamie Bisotti Software Engineer Lexmark International, Inc. - 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]
Parsing POMs (Maven 1.x) API - tips?
Hi, I need to parse a POM to read its properties and data. Currently I am opening a MavenSession to do this and it works good. There are drawbacks, however: 1. If the file changes, I need to reopen a MavenSession to have the POM updated 2. Performance-wise What would be the best way to do this? Perhaps using the same low-level API that the MavenSession uses? Your tips are welcome - 10x
Re: [M2] plugins language?
On Apr 11, 2005 6:04 PM, Brett Porter [EMAIL PROTECTED] wrote: Java. Thats my sort of talk.. Talk of beanshell and groovy makes me nauseous. The instructions to check out the source code give the cvs details, is this the head version or is there a svn repository? I'm not fussy which I've just been caught out before on other projects that moved to svn before the docs caught up. Mark On Apr 12, 2005 2:02 AM, Yuriy Ivanov [EMAIL PROTECTED] wrote: but What lang will be used for core plugins? - Original Message - From: Emmanuel Venisse [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Monday, April 11, 2005 6:25 PM Subject: Re: [M2] plugins language? Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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: Parsing POMs (Maven 1.x) API - tips?
http://cvs.mevenide.codehaus.org/mevenide-config/src/java/org/mevenide/context/ package over the mevenide. by giving it a directory with pom it loads the project.xml and properties files. IQueryContext con = new DefaultQueryContext(directory); Project proj = con.getPOMContext().getFinalProject(); the returned project should be a merge of pom + all it's parents. you can also get a project instance for each layer separately and similar things. it does not fire changes in files, but whenever you access the data, it will check timestamps for the project files and reload the data. regards Milos Kleint On Apr 11, 2005 9:36 PM, Arik Kfir [EMAIL PROTECTED] wrote: Hi, I need to parse a POM to read its properties and data. Currently I am opening a MavenSession to do this and it works good. There are drawbacks, however: 1. If the file changes, I need to reopen a MavenSession to have the POM updated 2. Performance-wise What would be the best way to do this? Perhaps using the same low-level API that the MavenSession uses? Your tips are welcome - 10x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parsing POMs (Maven 1.x) API - tips?
Milos Kleint wrote: by giving it a directory with pom it loads the project.xml and properties files. IQueryContext con = new DefaultQueryContext(directory); Project proj = con.getPOMContext().getFinalProject(); 10x milos - sounds great. Does it implement the parsing by itself, or use Maven API under the hood? it does not fire changes in files, but whenever you access the data, it will check timestamps for the project files and reload the data. Good enough I believe ;-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parsing POMs (Maven 1.x) API - tips?
On Apr 11, 2005 9:57 PM, Arik Kfir [EMAIL PROTECTED] wrote: Milos Kleint wrote: by giving it a directory with pom it loads the project.xml and properties files. IQueryContext con = new DefaultQueryContext(directory); Project proj = con.getPOMContext().getFinalProject(); 10x milos - sounds great. well, there's room for improvement. Currently some data loading is not indefinitely recursive, but 2 levels of inheritance are ok. Does it implement the parsing by itself, or use Maven API under the hood? itself, using jdom. I couldn't find anything that did what I needed. Like splitting the project definition based on locations. That allows us in the IDE integration to figure what is defined where and move it for example. it does not fire changes in files, but whenever you access the data, it will check timestamps for the project files and reload the data. Good enough I believe ;-) the idea here was that the IDE usually has means of listening to changes of documents/files. Milos - 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]
Maven2 maven.jar properties
In maven2, how do I specify the classpath, main class for the manifest? How I specify a manifest file to include? If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: 'maven.repo.local' not honored by all
I'm seeing the problem on Windows XP SP2, with Maven 1.0.2; haven't even looked at Maven 2 yet. Jamie On Apr 11, 2005 2:36 PM, Mark Lowe [EMAIL PROTECTED] wrote: If its useful I've got the same thing happening on OSX.. I symlink to a setup script that sets the varibles as I like them and its not digging.. #maven setup script. export M2_HOME=/Developer/Java/Maven2 export PATH=$M2_HOME/bin:$PATH export JAVA_HOME=/Library/Java/Home export M2_HOME_LOCAL=~/Library/Maven2 m2 -Dmaven.repo.local=$M2_HOME_LOCAL $@ Works fine with maven 1.0.. I'll have a dig through the sources and see if there are anychanges to the variable names. Mark On Apr 11, 2005 6:34 PM, Brett Porter [EMAIL PROTECTED] wrote: This should work, and I've never seen this happen. Please file it in JIRA for further investigation. - Brett On Apr 12, 2005 2:16 AM, Jamie Bisotti [EMAIL PROTECTED] wrote: Anyone??? On Apr 8, 2005 3:12 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: In my project.properties file, I set maven.repo.local=C:\blah\repository. I then proceeded to blow away %HOMEDRIVE%%HOMEPATH%\.maven\repository. Then I ran maven java:compile. I see where it downloads my project;s dependencies, and it places them in the appropriate local repository location. However, it also downloads commons-lang, antlr commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug? -- Jamie -- Jamie Bisotti Software Engineer Lexmark International, Inc. - 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] -- Jamie Bisotti Software Engineer Lexmark International, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Test Goal - Junit] Where have SystemOut and SystemErr gone ?
Hello, When I run my test goal with MyTest.java, I can not find in TEST-MyTest.xml the output of SystemOut and SystemErr. Instead, I have empty elements system-out![CDATA[]]/system-out system-err![CDATA[]]/system-err . I try to play with junit task parameters without success. Does anyone have a clue ? Thanks in advance, Cyrille Cyrille Le Clerc email : [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
possible to specify JAVA_HOME?
I'm building several project with maven, some of which build with a JAVA_HOME set to 1.4, some with 1.5 (aka Java5). So far, I can't get the 1.4 projects to build with a 1.5 JAVA_HOME, even if I set maven.compile.executable and maven.compile.source to 1.4. The build fails on our xjc task. The 1.4 installation handles XML differently, and has jar files in its endorsed directory. I'm actually calling maven from cruisecontrol, so I would prefer to be able to handle all of this from inside of maven somehow, and not have to modify my environment settings outside of maven. Then I can have one cruisecontrol job build everything, regardless of jdk version. One easy fix would be to specify a different JAVA_HOME for a build. Is there some way to do this? Thanks! --Chris
Re: possible to specify JAVA_HOME?
I also had a problem with java1.5+maven - what I did is modify the maven installation - I don't remember exactly what I did, but I know my "MAVEN_HOME/lib/endorsed" dir is empty, and I remember modifying the maven.bat file to NOT add the "-Djavax.xml.parser." and "-Djavax.xml.SAXParser" properties. The problem I think was that java5 changed the xml parser's package names, and caused some collisions. Perhaps there is a better solution someone here can suggest (I definitly don't like messing with Maven's home). Chris DeJong wrote: I'm building several project with maven, some of which build with a JAVA_HOME set to 1.4, some with 1.5 (aka Java5). So far, I can't get the 1.4 projects to build with a 1.5 JAVA_HOME, even if I set maven.compile.executable and maven.compile.source to 1.4. The build fails on our xjc task. The 1.4 installation handles XML differently, and has jar files in its endorsed directory. I'm actually calling maven from cruisecontrol, so I would prefer to be able to handle all of this from inside of maven somehow, and not have to modify my environment settings outside of maven. Then I can have one cruisecontrol job build everything, regardless of jdk version. One easy fix would be to specify a different JAVA_HOME for a build. Is there some way to do this? Thanks! --Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: possible to specify JAVA_HOME?
Use a shell script or batch file so you dont need to mess with maven's scripts, this makes things easier when upgrading maven also.. On windows your cursed with no symlinking but its still workable. Mark On Apr 11, 2005 11:36 PM, Arik Kfir [EMAIL PROTECTED] wrote: I also had a problem with java1.5+maven - what I did is modify the maven installation - I don't remember exactly what I did, but I know my MAVEN_HOME/lib/endorsed dir is empty, and I remember modifying the maven.bat file to NOT add the -Djavax.xml.parser. and -Djavax.xml.SAXParser properties. The problem I think was that java5 changed the xml parser's package names, and caused some collisions. Perhaps there is a better solution someone here can suggest (I definitly don't like messing with Maven's home). Chris DeJong wrote: I'm building several project with maven, some of which build with a JAVA_HOME set to 1.4, some with 1.5 (aka Java5). So far, I can't get the 1.4 projects to build with a 1.5 JAVA_HOME, even if I set maven.compile.executable and maven.compile.source to 1.4. The build fails on our xjc task. The 1.4 installation handles XML differently, and has jar files in its endorsed directory. I'm actually calling maven from cruisecontrol, so I would prefer to be able to handle all of this from inside of maven somehow, and not have to modify my environment settings outside of maven. Then I can have one cruisecontrol job build everything, regardless of jdk version. One easy fix would be to specify a different JAVA_HOME for a build. Is there some way to do this? Thanks! --Chris - 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]
[Jelly custom tag] Ant FileSet in a custom tag body
Hello, I needed a kind of test:test goal that can be called in maven.xml specifying the FileSet of involved Junit test cases (test:test relies on maven.test.reportsDirectory). To reach this need, I developped my own tag and I would like to pass the fileset as the body of the tag (see pseudo code below). Unfortunately, I do not succeed in using the ant:fileset in my custom tag. Does anyone have a clue on how to do this ? Thanks in advance, Cyrille. Cyrille Le Clerc email : [EMAIL PROTECTED] It would look like : !-- TAG DEFINITION -- define:tag name=my-test junit ... batchtest define:invokebody / !-- inject the 'parameter' -- /batchtest /junit /define:tag ... !-- USE CUSTOM TAG -- my-uir:my-test ant:fileset ant:include name=**/*Test / /ant:fileset my-uir:my-test - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 'maven.repo.local' not honored by all
I've never found this a problem with maven 1.* on any platform. How do you set %HOMEDRIVE% ? and (excuse the dumb question) what happens when you type echo %HOMEDRIVE% Mark On Apr 11, 2005 9:26 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: I'm seeing the problem on Windows XP SP2, with Maven 1.0.2; haven't even looked at Maven 2 yet. Jamie On Apr 11, 2005 2:36 PM, Mark Lowe [EMAIL PROTECTED] wrote: If its useful I've got the same thing happening on OSX.. I symlink to a setup script that sets the varibles as I like them and its not digging.. #maven setup script. export M2_HOME=/Developer/Java/Maven2 export PATH=$M2_HOME/bin:$PATH export JAVA_HOME=/Library/Java/Home export M2_HOME_LOCAL=~/Library/Maven2 m2 -Dmaven.repo.local=$M2_HOME_LOCAL $@ Works fine with maven 1.0.. I'll have a dig through the sources and see if there are anychanges to the variable names. Mark On Apr 11, 2005 6:34 PM, Brett Porter [EMAIL PROTECTED] wrote: This should work, and I've never seen this happen. Please file it in JIRA for further investigation. - Brett On Apr 12, 2005 2:16 AM, Jamie Bisotti [EMAIL PROTECTED] wrote: Anyone??? On Apr 8, 2005 3:12 PM, Jamie Bisotti [EMAIL PROTECTED] wrote: In my project.properties file, I set maven.repo.local=C:\blah\repository. I then proceeded to blow away %HOMEDRIVE%%HOMEPATH%\.maven\repository. Then I ran maven java:compile. I see where it downloads my project;s dependencies, and it places them in the appropriate local repository location. However, it also downloads commons-lang, antlr commons-jelly-tags-antlr, which I'm assuming Maven is using under the covers. That wouldn't be a problem, except they are still being put in %HOMEDRIVE%%HOMEPATH%\.maven\repository. Am I missing some other property, or is this a bug? -- Jamie -- Jamie Bisotti Software Engineer Lexmark International, Inc. - 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] -- Jamie Bisotti Software Engineer Lexmark International, Inc. - 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: REPOST: variable expansion in xdoc's?
Thanks for responding. Hopefully, this will be possible soon. I just submitted a patch which makes this possible. Here's the issue: http://jira.codehaus.org/browse/MPXDOC-140 mike --- Jörg Schaible [EMAIL PROTECTED] wrote: Eric Giguere wrote: Hello This link was posted releated to variable values in the navigation.xml. Maybe this will also work in other xdoc documents..? Check it out: http://cvs.apache.org/viewcvs.cgi/maven-plugins/pdf/src/plugin-test/xdocs/navigation.xml?rev=1.2view=markup Hope it helps Eric. No. Navigation.html is special and is a Velocity template. User provided xdocs are normal XML elements without any expansion. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploy
John, How about deployment? Can I specify deploymentRepository ?See exception below. Thanks! Leonid [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 deploy:deploy [INFO] [INFO] Building null [INFO] [INFO] maven-compiler-plugin: resolved to version 1.0-alpha-2-20050411.120835-1 from local repository [INFO] plexus-compiler-api: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler-javac: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compilers: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler-test: resolved to version 1.3-20050411.081334-1 from local repository [INFO] maven-artifact-test: resolved to version 2.0-20050411.072903-1 from local repository [INFO] maven: resolved to version 2.0-20050407.164450-2 from local repository [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Error configuring plugin for execution. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:144) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.plugin.PluginConfigurationException: The 'deploymentRepository' parameter is required for the execution of the deploy:deploy mojo and cannot be null. at org.apache.maven.plugin.DefaultPluginManager.getPluginConfigurationFromE xpressions(DefaultPluginManager.java:658) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:411) ... 13 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 18:37:55 EDT 2005 [INFO] Final Memory: 1M/73M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: [M2] plugins language?
It's in CVS, but only for a short time. I'll make sure the site stays up to date this time :) Cheers, Brett On Apr 12, 2005 4:42 AM, Mark Lowe [EMAIL PROTECTED] wrote: On Apr 11, 2005 6:04 PM, Brett Porter [EMAIL PROTECTED] wrote: Java. Thats my sort of talk.. Talk of beanshell and groovy makes me nauseous. The instructions to check out the source code give the cvs details, is this the head version or is there a svn repository? I'm not fussy which I've just been caught out before on other projects that moved to svn before the docs caught up. Mark On Apr 12, 2005 2:02 AM, Yuriy Ivanov [EMAIL PROTECTED] wrote: but What lang will be used for core plugins? - Original Message - From: Emmanuel Venisse [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Monday, April 11, 2005 6:25 PM Subject: Re: [M2] plugins language? Yura Ivanov said: Hi, I have a question Why will maven 2.0 use only java for writing plugins? I used maven 1.x enough long time, and always there were no enough documentation about using it and many useful thing I was looking in plugins scr. So it was very good place to dig if I had questions. My opinion that it could be not very comfortable for users of maven to look sorce code of plugins if they would be compiled, but I have never like jelly as scripting language. My suggestion is to use some java compatible scripting language for writing plugins, like BeanShell project or Groovy. You can use scripting langage for writing plugins. For this, you use marmalade. See at hello plugin. http://maven.apache.org/maven2/developing-plugins-with-marmalade.html Emmanuel - 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: Deploy
yes, distributionManagement repository idmy-deploy-repo/id urlscp://dist.mycompany.com/path/to/deploy/url /repository /distributionManagement We currently support file and SCP deployments. FTP should work if you add the wagon-ftp 1.0-alpha-2 JAR to your project. Username and password settings are configured in ~/.m2/settings.xml. Documentation will be forthcoming very shortly. Cheers, Brett On Apr 12, 2005 8:43 AM, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote: John, How about deployment? Can I specify deploymentRepository ?See exception below. Thanks! Leonid [EMAIL PROTECTED] /home/lilyevsk/workspace/lex $ m2 deploy:deploy [INFO] [INFO] Building null [INFO] [INFO] maven-compiler-plugin: resolved to version 1.0-alpha-2-20050411.120835-1 from local repository [INFO] plexus-compiler-api: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler-javac: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compilers: resolved to version 1.3-20050411.081334-1 from local repository [INFO] plexus-compiler-test: resolved to version 1.3-20050411.081334-1 from local repository [INFO] maven-artifact-test: resolved to version 2.0-20050411.072903-1 from local repository [INFO] maven: resolved to version 2.0-20050407.164450-2 from local repository [INFO] [ERROR] BUILD ERROR [INFO] [ERROR] Cause: org.apache.maven.plugin.PluginExecutionException: Error configuring plugin for execution. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeMojo(DefaultL ifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:144) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:212) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136) at org.apache.maven.cli.MavenCli.main(MavenCli.java:233) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) Caused by: org.apache.maven.plugin.PluginConfigurationException: The 'deploymentRepository' parameter is required for the execution of the deploy:deploy mojo and cannot be null. at org.apache.maven.plugin.DefaultPluginManager.getPluginConfigurationFromE xpressions(DefaultPluginManager.java:658) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:411) ... 13 more [INFO] [INFO] Total time: 1 seconds [INFO] Finished at: Mon Apr 11 18:37:55 EDT 2005 [INFO] Final Memory: 1M/73M [INFO] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 maven.jar properties
For the JAR plugin: configuration archive manifestFile.../manifestFile (not required to include the latter) manifest mainClass.../mainClass /manifest /archive /configuration see: manifest element: http://cvs.apache.org/viewcvs.cgi/maven-components/maven-archiver/src/main/java/org/apache/maven/archiver/ManifestConfiguration.java?rev=1.1view=markup archive element: http://cvs.apache.org/viewcvs.cgi/maven-components/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiveConfiguration.java?rev=1.1view=markup (we intend to include an automatic documentation generator for plugins in alpha-2) - Brett On Apr 12, 2005 5:14 AM, Ilyevsky, Leonid (Equity Trading) [EMAIL PROTECTED] wrote: In maven2, how do I specify the classpath, main class for the manifest? How I specify a manifest file to include? If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M1] Multiproject Frustration #1 - 'Clean' loads dependencies! Huh?
Hi Folks, I'm just getting started with Maven and not sure when the behaviour I expect is the behaviour intended by the authors. Either of the following commands fails the same way... maven -o -Dgoal=clean multiproject:goal or maven -o multiproject:clean Both result in : - o 0 o - Starting the reactor... Our processing order: Component1 CompMaint1 Component2 CompMaint2 Application2 Application1 + | Executing clean:clean Component1 | Memory: 3M/4M + multiproject:goal: [echo] Hello From Top Level : == maven.multiproject.aggregateDir= build:start: clean:clean: [delete] Deleting directory C:\tcool\experiments\maven\MDMQ\mpm\Target\Components\Component1 + | Executing clean:clean CompMaint1 | Memory: 3M/4M + BUILD FAILED File.. C:\Documents and Settings\tcool\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly Element... maven:reactor Line.. 217 Column 9 The build cannot continue because of the following unsatisfied dependency: mdmqmpm-component1-1.0.jar - o 0 o - ¿¿How can I tell the reactor to forget about dependencies when executing a 'clean' goal?? Thanks, TC __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M1] Multiproject Frustration #1 - 'Clean' loads dependencies! Huh?
you must clean and install at the same time, unfortunately - this is a known limitation in the Maven 1.x architecture. - Brett On Apr 12, 2005 9:12 AM, Trudy Cool [EMAIL PROTECTED] wrote: Hi Folks, I'm just getting started with Maven and not sure when the behaviour I expect is the behaviour intended by the authors. Either of the following commands fails the same way... maven -o -Dgoal=clean multiproject:goal or maven -o multiproject:clean Both result in : - o 0 o - Starting the reactor... Our processing order: Component1 CompMaint1 Component2 CompMaint2 Application2 Application1 + | Executing clean:clean Component1 | Memory: 3M/4M + multiproject:goal: [echo] Hello From Top Level : == maven.multiproject.aggregateDir= build:start: clean:clean: [delete] Deleting directory C:\tcool\experiments\maven\MDMQ\mpm\Target\Components\Component1 + | Executing clean:clean CompMaint1 | Memory: 3M/4M + BUILD FAILED File.. C:\Documents and Settings\tcool\.maven\cache\maven-multiproject-plugin-1.3.1\plugin.jelly Element... maven:reactor Line.. 217 Column 9 The build cannot continue because of the following unsatisfied dependency: mdmqmpm-component1-1.0.jar - o 0 o - ¿¿How can I tell the reactor to forget about dependencies when executing a 'clean' goal?? Thanks, TC __ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ - 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: [M1] Multiproject Frustration #1 - 'Clean' loads dependencies! Huh?
Dear Brett you must clean and install at the same time, unfortunately - this is a known limitation in the Maven 1.x architecture. Yeesh! Sorry! I hadn't seen that, or don't remember seeing it. Thanks for the speedy reply! TC __ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
