Re: svn commit: r521662 - in /maven/continuum/trunk: continuum-model/pom.xml pom.xml
Yes, with the actual version of Modello.
Without output directories, files are generated in wrong directories.
Emmanuel
Rahul Thakur a écrit :
Do we really need to specify the outputDirectory?
Eclipse barfs on output folders being added as source directories and
flags build errors (Eclipse related) on all dependent projects.
Rahul
On 3/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Fri Mar 23 03:31:35 2007
New Revision: 521662
URL: http://svn.apache.org/viewvc?view=revrev=521662
Log:
Use the released modello
Fix the build with the new modello
Modified:
maven/continuum/trunk/continuum-model/pom.xml
maven/continuum/trunk/pom.xml
Modified: maven/continuum/trunk/continuum-model/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-model/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/continuum-model/pom.xml (original)
+++ maven/continuum/trunk/continuum-model/pom.xml Fri Mar 23 03:31:35
2007
@@ -46,6 +46,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+
outputDirectory${basedir}/target/classes/META-INF/outputDirectory
/configuration
/execution
execution
@@ -55,6 +56,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+
outputDirectory${basedir}/target/classes/META-INF/outputDirectory
replicationParameterstrue/replicationParameters
/configuration
/execution
Modified: maven/continuum/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/pom.xml (original)
+++ maven/continuum/trunk/pom.xml Fri Mar 23 03:31:35 2007
@@ -74,7 +74,7 @@
plugin
groupIdorg.codehaus.modello/groupId
artifactIdmodello-maven-plugin/artifactId
- version1.0-alpha-15-SNAPSHOT/version
+ version1.0-alpha-15/version
/plugin
/plugins
/pluginManagement
Re: XML RPC security
Maybe, but I can't find it.
Emmanuel
Rahul Thakur a écrit :
I thought there was something similar to this that exists in Redback?
Rahul
- Original Message - From: Emmanuel Venisse
[EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Saturday, April 28, 2007 12:37 AM
Subject: Re: XML RPC security
I think it's best solution. With a token, we don't have login/password
over the network for each request.
XmlRpcService
String login( username, password ) //return a token
{
tokenManager.login( username, password );
}
Object method1( token, params ) //null token for guest user or a
getGuestToken() method that will return it
{
User user = tokenManager.getUser( token );
...
}
Object method2( token, params )
{
...
}
TokenManager
String login( username, password ); //return a token
User getUser( token )
The TokenManager can be a plexus component with a default
implementation for redback.
wdyt?
Emmanuel
Emmanuel Venisse a écrit :
Hey guys,
Some quick notes on the security for XML RPC interface. This is what I
am thinking...
Have an AuthenticatedXmlRpcService component that services the xml rpc
requests. The first request from a client to the service is a request
for authentication. A successful authentication returns an
authentication Token, which is passed along with subsequent requests by
the client. A Token can go stale (configurable time period?) if there
were not requests detected for it. Also, we could have a service that
answers any polling requests and keeps a Token 'alive'.
Thoughts?
Rahul
Re: svn commit: r521662 - in /maven/continuum/trunk: continuum-model/pom.xml pom.xml
So we need to fix modello to output resources to correct directories,
right?
(I'd hate to swtich IDEs just for this ;-) )
Rahul
- Original Message -
From: Emmanuel Venisse [EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Monday, April 30, 2007 9:30 PM
Subject: Re: svn commit: r521662 - in /maven/continuum/trunk:
continuum-model/pom.xml pom.xml
Yes, with the actual version of Modello.
Without output directories, files are generated in wrong directories.
Emmanuel
Rahul Thakur a écrit :
Do we really need to specify the outputDirectory?
Eclipse barfs on output folders being added as source directories and
flags build errors (Eclipse related) on all dependent projects.
Rahul
On 3/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Fri Mar 23 03:31:35 2007
New Revision: 521662
URL: http://svn.apache.org/viewvc?view=revrev=521662
Log:
Use the released modello
Fix the build with the new modello
Modified:
maven/continuum/trunk/continuum-model/pom.xml
maven/continuum/trunk/pom.xml
Modified: maven/continuum/trunk/continuum-model/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-model/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/continuum-model/pom.xml (original)
+++ maven/continuum/trunk/continuum-model/pom.xml Fri Mar 23
03:31:35 2007
@@ -46,6 +46,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+
outputDirectory${basedir}/target/classes/META-INF/outputDirectory
/configuration
/execution
execution
@@ -55,6 +56,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+
outputDirectory${basedir}/target/classes/META-INF/outputDirectory
replicationParameterstrue/replicationParameters
/configuration
/execution
Modified: maven/continuum/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/pom.xml (original)
+++ maven/continuum/trunk/pom.xml Fri Mar 23 03:31:35 2007
@@ -74,7 +74,7 @@
plugin
groupIdorg.codehaus.modello/groupId
artifactIdmodello-maven-plugin/artifactId
- version1.0-alpha-15-SNAPSHOT/version
+ version1.0-alpha-15/version
/plugin
/plugins
/pluginManagement
Re: svn commit: r521662 - in /maven/continuum/trunk: continuum-model/pom.xml pom.xml
Rahul Thakur a écrit :
So we need to fix modello to output resources to correct directories,
right?
Yes.
(I'd hate to swtich IDEs just for this ;-) )
Rahul
- Original Message - From: Emmanuel Venisse
[EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Monday, April 30, 2007 9:30 PM
Subject: Re: svn commit: r521662 - in /maven/continuum/trunk:
continuum-model/pom.xml pom.xml
Yes, with the actual version of Modello.
Without output directories, files are generated in wrong directories.
Emmanuel
Rahul Thakur a écrit :
Do we really need to specify the outputDirectory?
Eclipse barfs on output folders being added as source directories and
flags build errors (Eclipse related) on all dependent projects.
Rahul
On 3/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Fri Mar 23 03:31:35 2007
New Revision: 521662
URL: http://svn.apache.org/viewvc?view=revrev=521662
Log:
Use the released modello
Fix the build with the new modello
Modified:
maven/continuum/trunk/continuum-model/pom.xml
maven/continuum/trunk/pom.xml
Modified: maven/continuum/trunk/continuum-model/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-model/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/continuum-model/pom.xml (original)
+++ maven/continuum/trunk/continuum-model/pom.xml Fri Mar 23
03:31:35 2007
@@ -46,6 +46,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+ outputDirectory${basedir}/target/classes/META-INF/outputDirectory
/configuration
/execution
execution
@@ -55,6 +56,7 @@
/goals
configuration
modelsrc/main/mdo/continuum.xml/model
+ outputDirectory${basedir}/target/classes/META-INF/outputDirectory
replicationParameterstrue/replicationParameters
/configuration
/execution
Modified: maven/continuum/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/trunk/pom.xml?view=diffrev=521662r1=521661r2=521662
==
--- maven/continuum/trunk/pom.xml (original)
+++ maven/continuum/trunk/pom.xml Fri Mar 23 03:31:35 2007
@@ -74,7 +74,7 @@
plugin
groupIdorg.codehaus.modello/groupId
artifactIdmodello-maven-plugin/artifactId
- version1.0-alpha-15-SNAPSHOT/version
+ version1.0-alpha-15/version
/plugin
/plugins
/pluginManagement
Re: XML RPC security
I don't think you need to handle the authentication part in the
continuum code, nor need to create tokens,...
If you use standard Digest authentication the password is encrypted,
and if you tie that with https then it's completely secure.
Acegi uses a filter to process all the requests and populate the auth
info or return the standard http codes if user not authenticated
http://www.acegisecurity.org/docbook/acegi.html#digest
On 4/30/07, Jesse McConnell [EMAIL PROTECTED] wrote:
I am hoping to get a couple of authn and authz web services running in
redback this week, once I finish up the role profile refactor and
clean up, I want to wack out a webservice and then start getting
continuum integrated to using the new redback setup.
sounds like that would work perfectly for this xml-rpc stuff in continuum.
rahul, planning on using xfire until the apache CXF stuff gets it
first release out of the incubator...that sound good?
jesse
On 4/30/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Maybe, but I can't find it.
Emmanuel
Rahul Thakur a écrit :
I thought there was something similar to this that exists in Redback?
Rahul
- Original Message - From: Emmanuel Venisse
[EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Saturday, April 28, 2007 12:37 AM
Subject: Re: XML RPC security
I think it's best solution. With a token, we don't have login/password
over the network for each request.
XmlRpcService
String login( username, password ) //return a token
{
tokenManager.login( username, password );
}
Object method1( token, params ) //null token for guest user or a
getGuestToken() method that will return it
{
User user = tokenManager.getUser( token );
...
}
Object method2( token, params )
{
...
}
TokenManager
String login( username, password ); //return a token
User getUser( token )
The TokenManager can be a plexus component with a default
implementation for redback.
wdyt?
Emmanuel
Emmanuel Venisse a écrit :
Hey guys,
Some quick notes on the security for XML RPC interface. This is what I
am thinking...
Have an AuthenticatedXmlRpcService component that services the xml rpc
requests. The first request from a client to the service is a request
for authentication. A successful authentication returns an
authentication Token, which is passed along with subsequent requests by
the client. A Token can go stale (configurable time period?) if there
were not requests detected for it. Also, we could have a service that
answers any polling requests and keeps a Token 'alive'.
Thoughts?
Rahul
--
jesse mcconnell
[EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: XML RPC security
I have never really messed with authenticated web services at all so
not sure what to say..
I'll take a look through that though, thanks carlos
jesse
On 4/30/07, Carlos Sanchez [EMAIL PROTECTED] wrote:
I don't think you need to handle the authentication part in the
continuum code, nor need to create tokens,...
If you use standard Digest authentication the password is encrypted,
and if you tie that with https then it's completely secure.
Acegi uses a filter to process all the requests and populate the auth
info or return the standard http codes if user not authenticated
http://www.acegisecurity.org/docbook/acegi.html#digest
On 4/30/07, Jesse McConnell [EMAIL PROTECTED] wrote:
I am hoping to get a couple of authn and authz web services running in
redback this week, once I finish up the role profile refactor and
clean up, I want to wack out a webservice and then start getting
continuum integrated to using the new redback setup.
sounds like that would work perfectly for this xml-rpc stuff in continuum.
rahul, planning on using xfire until the apache CXF stuff gets it
first release out of the incubator...that sound good?
jesse
On 4/30/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Maybe, but I can't find it.
Emmanuel
Rahul Thakur a écrit :
I thought there was something similar to this that exists in Redback?
Rahul
- Original Message - From: Emmanuel Venisse
[EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Saturday, April 28, 2007 12:37 AM
Subject: Re: XML RPC security
I think it's best solution. With a token, we don't have login/password
over the network for each request.
XmlRpcService
String login( username, password ) //return a token
{
tokenManager.login( username, password );
}
Object method1( token, params ) //null token for guest user or a
getGuestToken() method that will return it
{
User user = tokenManager.getUser( token );
...
}
Object method2( token, params )
{
...
}
TokenManager
String login( username, password ); //return a token
User getUser( token )
The TokenManager can be a plexus component with a default
implementation for redback.
wdyt?
Emmanuel
Emmanuel Venisse a écrit :
Hey guys,
Some quick notes on the security for XML RPC interface. This is what I
am thinking...
Have an AuthenticatedXmlRpcService component that services the xml rpc
requests. The first request from a client to the service is a request
for authentication. A successful authentication returns an
authentication Token, which is passed along with subsequent requests by
the client. A Token can go stale (configurable time period?) if there
were not requests detected for it. Also, we could have a service that
answers any polling requests and keeps a Token 'alive'.
Thoughts?
Rahul
--
jesse mcconnell
[EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
--
jesse mcconnell
[EMAIL PROTECTED]
Re: ApacheCon EU
Brett Porter wrote: Hi, I saw that Dennis, Jason, Kenney, Eric, Martin, Robert, and Arnaud B will all be at AC EU next week - is anyone else attending ApacheCon? I think it would be good to get some time in front of a white board to go through a couple of the big issues while we have the opportunity for face time and to hack some things together. It sounds like the same opportunity will present itself at JavaOne too. Of course, we can discuss some in real time with people on IRC and bring any output back to the list so everyone gets a chance to participate. Sound good. What day/time would suit people? I'm flexible. Maybe the following are appropriate for AC: - anything more we can do for releases (polish up the staging stuff, incorporate RAT, ...?) - plugin integration testing and unit testing - roadmap discussion / highlighting other issues I'm especially interested in different testing techniques for plugins. Any other thoughts? Interest from the folks attending in anything in particular? - Brett -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release the maven-release-plugin?
Stephane, you can send the vote and release it, I'll continue on the next version. Emmanuel Stephane Nicoll a écrit : Emmanuel is still working on the release manager so I need to check with him before releasing the manager and the plugin. Emmanuel? Thanks, Stéphane On 4/29/07, Robert Kopco [EMAIL PROTECTED] wrote: Is there any progress on that? 2007/4/20, Stephane Nicoll [EMAIL PROTECTED]: Okay. I am taking care of that and I'll cast for a vote tonight. (Unless someone wants to do it earlier) Cheers, Stéphane On 4/20/07, Dan Tran [EMAIL PROTECTED] wrote: +1, please cut beta-5 On 4/19/07, Brian E. Fox [EMAIL PROTECTED] wrote: I agree. Why not release beta-5 now and then 6 when your changes are ready? -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 10:14 AM To: Maven Developers List Subject: Re: Release the maven-release-plugin? I think it makes sense to release a beta-5 if the changes are major enough. There's nothing that prevents you from releasing beta-6 or -rc1 afterwards. Robert, I'll have a look to the issues now. Thanks, Stéphane On 4/19/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: I'd like to add more features in this plugin before to release it like branch creation, check SNAPSHOTS in properties and not used in dependencies versions For the moment, the release is planned to be done in one month, after the release of Maven-SCM 1.0 final. Emmanuel Robert Kopco a écrit : Thank you very much! Now there are 19 of 25 issues fixed. In would be very happy if the current state could be released as 2.0-beta-5. The rest should be moved to the next version. Besides MRELEASE-6 (which has been open for 1 1/2 years) none of the remaining issues is critical. What do you think? Best regards, Robert 2007/4/15, Stephane Nicoll [EMAIL PROTECTED]: On 4/15/07, Robert Kopco [EMAIL PROTECTED] wrote: It has been 11 month since the last release of the maven-release-plugin. When will the next release of the plugin approximately be? There are 10 open issues. For a lot of issues patches have been provided: MRELEASE-128 MRELEASE-122 MRELEASE-116 MRELEASE-90 MRELEASE-91 MRELEASE-137 Maybe a committer could have a look at one of these. Will do. Thanks, Stéphane _ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden! - 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] _ Sie suchen E-Mails, Dokumente oder Fotos? Die neue MSN Suche Toolbar mit Windows-Desktopsuche liefert in sekundenschnelle Ergebnisse. Jetzt neu! http://desktop.msn.de/ Jetzt gratis downloaden! - 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: [M1][vote] release plugins : idea 1.7, jalopy 1.5.1, jar 1.8.1, javadoc 1.9, multichanges 1.3, plugin 1.7.1
I'll release all these plugins. the vote passed with 3 binding (Lukas, Stephane, Me) and 1 non-binding (Jeff) Arnaud On 25/04/07, Stephane Nicoll [EMAIL PROTECTED] wrote: +1 Stéphane On 4/24/07, Lukas Theussl [EMAIL PROTECTED] wrote: +1 -Lukas Arnaud HERITIER wrote: Here is a new list of plugins to release for maven 1.x. -- IDEA 1.7 -- Changes in this version include : New Features: o Autodetect which version control system to use Fixes MPIDEA-43. Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-idea-plugin -Dversion=1.7-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/idea/ -- JALOPY 1.5.1 -- Changes in this version include : New Features: o Add a property that controls the source code encoding. Fixes MPJALOPY-12. Thanks to Joachim Bader. Changes: o Upgrade plexus-utils to version 1.0.5 Fixes MAVEN-1803. Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jalopy-plugin -Dversion=1.5.1-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/jalopy/ -- JAR 1.8.1 -- Changes in this version include : Changes: o Change the default repository to http://repo1.maven.org/maven/ for dependencies url in the manifest. Fixes MAVEN-1789. o Update to velocity 1.5. Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jar-plugin -Dversion=1.8.1-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/jar/ -- JAVADOC 1.9 -- Changes : Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-javadoc-plugin -Dversion=1.9-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/javadoc/ -- MULTICHANGES 1.3 -- Changes in this version include : New Features: o New page to describe the next releases. o New RSS feed for releases. Changes: o New internal format to store information about releases. o Remove usage of the deprecated dependency-handle tag. Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-multichanges-plugin -Dversion=1.3-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/multichanges/ -- PLUGIN 1.7.1 -- Changes in this version include : Fixed bugs: o assert:assertPluginAvailable : Fix error (NoSuchElementException) if the minimum release number has less elements than the version number installed. Changes: o Don't check that a given plugin version is available in the bootstrap. o Update dependencies to unify them between plugins. The following dependencies are updated : commons-jelly-tags-interaction v1.0 to v1.1, jaxen v1.0-FCS-full to 1.1-beta-9. The following dependencies are removed : saxpath. o Upgrade to Xerces 2.8.0. Replace the deprecated xmlParserAPIs by xml-apis 1.3.03. Add the xml-resolver dependency for xerces. Fixes MAVEN-1753. Download : maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-plugin-plugin -Dversion=1.7.1-SNAPSHOT Staging site : http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/plugin/ Normal voting rules, 72 hours, +1/0/-1 My +1 for all Arnaud - 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]
axis2-wsdl2code-maven-plugin
Hi list, do you know who has developed axis2-wsdl2code-maven-plugin ? A few days ago, I asked a question concerning this plugin on [EMAIL PROTECTED] There was no reaction at all. I could work around my problem using the ant plugin, but I like to use axis2-wsdl2code-maven-plugin. Thank you in advance Armin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin
On 4/30/07, Armin Ehrenfels [EMAIL PROTECTED] wrote: do you know who has developed axis2-wsdl2code-maven-plugin ? A few days ago, I asked a question concerning this plugin on [EMAIL PROTECTED] There was no reaction at all. I could work around my problem using the ant plugin, but I like to use axis2-wsdl2code-maven-plugin. Was me. Unfortunately, I am not reading axis2-dev, so you'd better ask here. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin
Jochen Wiedmann wrote: On 4/30/07, Armin Ehrenfels [EMAIL PROTECTED] wrote: do you know who has developed axis2-wsdl2code-maven-plugin ? A few days ago, I asked a question concerning this plugin on [EMAIL PROTECTED] There was no reaction at all. I could work around my problem using the ant plugin, but I like to use axis2-wsdl2code-maven-plugin. Was me. Unfortunately, I am not reading axis2-dev, so you'd better ask here. Jochen Jochen thank you for your quick response. Below the content of my email to axis2-dev: I'm trying to find out how to specify a bindingfile for the JiBX in my pom.xml. What I have found so far is the unit test org.apache.*axis2*.jibx.Test which shows how to programmatically add the bindingfile option to the options map. The test succeeds, but it seems that there is no integration test with *WSDL2CodeMojo*. Also, as far as I could find out, the mojo wouldn't evaluate Ebindingfile anyway which is obviously reasonable since it's a JiBX specific option. Are my findings correct and if so, is there work in progress on that ? Regards Armin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release maven ant plugin 2.0
Hi Carlos, We need to release the maven-install-plugin before. Cheers, Vincent 2007/4/24, Vincent Siveton [EMAIL PROTECTED]: I will have a look this week. Thanks, Vincent 2007/4/20, Carlos Sanchez [EMAIL PROTECTED]: Vincent is the most active with the plugin, so i didn't want to apply it if he already didn't I was waiting to hear his opinion in this thread On 4/14/07, Brian E. Fox [EMAIL PROTECTED] wrote: MANT-22 has a patch and it seems pretty trivial. Why not apply it? I don't use mant much so maybe I'm missing something obvious. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Saturday, April 14, 2007 11:48 AM To: Maven Developers List Subject: [VOTE] Release maven ant plugin 2.0 I'd like to release the maven ant plugin for Maven 2. Last release was a year ago Specially addressed to Vincent Siveton, as he has been the one working more on it. https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ant-plugin rev# 528823 deployed as 2.0-SNAPSHOT Roadmap http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11124 fixfor=12933 I'd push MANT-22 for the next release -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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]
[ANN] Maven IDEA Plugin 1.7 for Maven 1.x released
We are pleased to announce the Maven IDEA Plugin 1.7 release! http://maven.apache.org/maven-1.x/plugins/idea/ IDEA Plugin for Maven. === Changes in this version include: New Features: o Autodetect which version control system to use Fixes MPIDEA-43. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-idea-plugin -Dversion=1.7 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-idea-plugin-1.7.jar === Issues, bugs, and feature requests for Maven IDEA Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPIDEA Have fun! -The Maven IDEA Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Jar Plugin 1.8.1 for Maven 1.x released
We are pleased to announce the Maven Jar Plugin 1.8.1 release! http://maven.apache.org/maven-1.x/plugins/jar/ Plugin for creating JAR files. === Changes in this version include: Changes: o Change the default repository to http://repo1.maven.org/maven/ for dependencies url in the manifest. Fixes MAVEN-1789. o Update to velocity 1.5. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jar-plugin -Dversion=1.8.1 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-jar-plugin-1.8.1.jar === Issues, bugs, and feature requests for Maven Jar Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPJAR Have fun! -The Maven Jar Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Plugin Plugin 1.7.1 for Maven 1.x released
We are pleased to announce the Maven Plugin Plugin 1.7.1 release! http://maven.apache.org/maven-1.x/plugins/plugin/ Maven Plugin management plugin. === Changes in this version include: Fixed bugs: o assert:assertPluginAvailable : Fix error (NoSuchElementException) if the minimum release number has less elements than the version number installed. o plugin:install fails if maven.jar.final.name is set. Fixes MPPLUGIN-35. Changes: o Don't check that a given plugin version is available in the bootstrap. o Update dependencies to unify them between plugins. The following dependencies are updated : commons-jelly-tags-interaction v1.0 to v1.1, jaxen v1.0-FCS-full to 1.1-beta-9. The following dependencies are removed : saxpath. o Upgrade to Xerces 2.8.0. Replace the deprecated xmlParserAPIs by xml-apis 1.3.03. Add the xml-resolver dependency for xerces. Fixes MAVEN-1753. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-plugin-plugin -Dversion=1.7.1 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-plugin-plugin-1.7.1.jar === Issues, bugs, and feature requests for Maven Plugin Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPPLUGIN Have fun! -The Maven Plugin Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Jalopy Plugin 1.5.1 for Maven 1.x released
We are pleased to announce the Maven Jalopy Plugin 1.5.1 release! http://maven.apache.org/maven-1.x/plugins/jalopy/ === Changes in this version include: New Features: o Add a property that controls the source code encoding. Fixes MPJALOPY-12. Thanks to Joachim Bader. Changes: o Upgrade plexus-utils to version 1.0.5 Fixes MAVEN-1803. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jalopy-plugin -Dversion=1.5.1 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-jalopy-plugin-1.5.1.jar === Issues, bugs, and feature requests for Maven Jalopy Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPJALOPY Have fun! -The Maven Jalopy Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Javadoc Plugin 1.9 for Maven 1.x released
We are pleased to announce the Maven Javadoc Plugin 1.9 release! http://maven.apache.org/maven-1.x/plugins/javadoc/ === Changes in this version include: New Features: o Add specifying params with alternate doclets. Fixes MPJAVADOC-80. Fixed bugs: o Do not add a directory of sources which doesn't exist. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-javadoc-plugin -Dversion=1.9 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-javadoc-plugin-1.9.jar === Issues, bugs, and feature requests for Maven Javadoc Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPJAVADOC Have fun! -The Maven Javadoc Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven MultiChanges Plugin 1.3 for Maven 1.x released
We are pleased to announce the Maven MultiChanges Plugin 1.3 release! http://maven.apache.org/maven-1.x/plugins/multichanges/ Produce release dashboard for subprojects. === Changes in this version include: New Features: o New page to describe the next releases. o New RSS feed for releases. Changes: o New internal format to store information about releases. o Remove usage of the deprecated dependency-handle tag. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-multichanges-plugin -Dversion=1.3 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-multichanges-plugin-1.3.jar === Issues, bugs, and feature requests for Maven MultiChanges Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPMULTICHANGES Have fun! -The Maven MultiChanges Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XML RPC security
I am hoping to get a couple of authn and authz web services running in
redback this week, once I finish up the role profile refactor and
clean up, I want to wack out a webservice and then start getting
continuum integrated to using the new redback setup.
sounds like that would work perfectly for this xml-rpc stuff in continuum.
rahul, planning on using xfire until the apache CXF stuff gets it
first release out of the incubator...that sound good?
jesse
On 4/30/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
Maybe, but I can't find it.
Emmanuel
Rahul Thakur a écrit :
I thought there was something similar to this that exists in Redback?
Rahul
- Original Message - From: Emmanuel Venisse
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 28, 2007 12:37 AM
Subject: Re: XML RPC security
I think it's best solution. With a token, we don't have login/password
over the network for each request.
XmlRpcService
String login( username, password ) //return a token
{
tokenManager.login( username, password );
}
Object method1( token, params ) //null token for guest user or a
getGuestToken() method that will return it
{
User user = tokenManager.getUser( token );
...
}
Object method2( token, params )
{
...
}
TokenManager
String login( username, password ); //return a token
User getUser( token )
The TokenManager can be a plexus component with a default
implementation for redback.
wdyt?
Emmanuel
Emmanuel Venisse a écrit :
Hey guys,
Some quick notes on the security for XML RPC interface. This is what I
am thinking...
Have an AuthenticatedXmlRpcService component that services the xml rpc
requests. The first request from a client to the service is a request
for authentication. A successful authentication returns an
authentication Token, which is passed along with subsequent requests by
the client. A Token can go stale (configurable time period?) if there
were not requests detected for it. Also, we could have a service that
answers any polling requests and keeps a Token 'alive'.
Thoughts?
Rahul
--
jesse mcconnell
[EMAIL PROTECTED]
Re: svn commit: r533512 - /maven/plugins/trunk/maven-gpg-plugin/pom.xml
On Sunday 29 April 2007 10:33, Jason van Zyl wrote: On 29 Apr 07, at 10:24 AM 29 Apr 07, [EMAIL PROTECTED] wrote: URL: http://svn.apache.org/viewvc?view=revrev=533512 Log: Update pre-req to maven 2.0.5 (2.0.4 doesn't allow proper signing of the poms) This is because the POM is no longer modified by the installation process. So you could hack around it, but it's probably not worth it and most people can use 2.0.5. Agreed. Making the prerequisite just be 2.0.5 makes it easier. I hate putting a bunch of hacks in place to support an old version when they should just be able to use the newer version without issues. Dan Jason. Modified: maven/plugins/trunk/maven-gpg-plugin/pom.xml Modified: maven/plugins/trunk/maven-gpg-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-gpg- plugin/pom.xml?view=diffrev=533512r1=533511r2=533512 == --- maven/plugins/trunk/maven-gpg-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-gpg-plugin/pom.xml Sun Apr 29 07:24:27 2007 @@ -10,7 +10,7 @@ version1.0-alpha-4-SNAPSHOT/version namemaven-gpg-plugin Maven Mojo/name prerequisites -maven2.0/maven +maven2.0.5/maven /prerequisites issueManagement systemjira/system - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Removing MUAS jira project
There's a maven-upload-applications MUAS project in jira that I never heard about, any problem with deleting it as it's already covered with MAVENUPLOAD and MEV ? -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Artifact version range behavior bug?
Plugins seem to resolve version ranges in an inconsistent manor. If I have a dependency version specified as [1.0,) how should this be resolved with respect to SNAPSHOTS (in the opinion of the maven2 developers)? Test case: Assume you have released versions 1.0, 1.1, 1.2, 1.3, 1.4 1.5. In addition snapshot releases exist for all versions as well as 1.6-SNAPSHOT. Behavior: Currently the idea, assembly dependency plugis resolve this to version 1.6-SNAPSHOT, however the release plugin trunk logic does not, it will resolve this to 1.5 (prior beta releases did resolve to 1.6-SNAPSHOT). In my opinion the later case is how it should behave (resolve to 1.5); set-notation should never resolve to SNAPSHOTS. We use set-notation as our primary dependency management technique for artifacts created inhouse. We unbound the high end of the version to mean we want the latest released version. If we want SNAPSHOTS to be included we manually change the version to state this. Depending on the opinion of the maven2 developers, another option that I think would also work well is to have another tag in the dependency section turning on/off inclusion of snapshots, i.e. includeSnapshots. -- View this message in context: http://www.nabble.com/Artifact-version-range-behavior-bug--tf3670887s177.html#a10257365 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin
On 4/30/07, Armin Ehrenfels [EMAIL PROTECTED] wrote: I'm trying to find out how to specify a bindingfile for the JiBX in my pom.xml. Please understand, that I've got absolutely no idea about JiBX. I do not know, what's required for a JiBX binding or not. I do not know, whether the binding file is required at runtime, at compile time or whenever else. You've got to tell me more details. integration test with *WSDL2CodeMojo*. Also, as far as I could find out, the mojo wouldn't evaluate Ebindingfile anyway which is obviously reasonable since it's a JiBX specific option. If there is a requirement for these things, we've got to solve it. Does the Ant task have something comparable? Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Jar Plugin 1.8.1 for Maven 1.x released
We are pleased to announce the Maven Jar Plugin 1.8.1 release! http://maven.apache.org/maven-1.x/plugins/jar/ Plugin for creating JAR files. === Changes in this version include: Changes: o Change the default repository to http://repo1.maven.org/maven/ for dependencies url in the manifest. Fixes MAVEN-1789. o Update to velocity 1.5. === To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jar-plugin -Dversion=1.8.1 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-jar-plugin-1.8.1.jar === Issues, bugs, and feature requests for Maven Jar Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPJAR Have fun! -The Maven Jar Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Jar Plugin 1.8.1 for Maven 1.x released
sorry for the noise .. Arnaud On 30/04/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We are pleased to announce the Maven Jar Plugin 1.8.1 release! http://maven.apache.org/maven-1.x/plugins/jar/ Plugin for creating JAR files. === Changes in this version include: Changes: o Change the default repository to http://repo1.maven.org/maven/ for dependencies url in the manifest. Fixes MAVEN-1789. o Update to velocity 1.5. === To automatically install the plugin, type the following on a single line: maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-jar-plugin -Dversion=1.8.1 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-jar-plugin-1.8.1.jar === Issues, bugs, and feature requests for Maven Jar Plugin should be submitted to the following issue tracking system: http://jira.codehaus.org/browse/MPJAR Have fun! -The Maven Jar Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remove auto-resolution of plugin versions from Maven 2.1
On 4/11/07, John Casey [EMAIL PROTECTED] wrote: Hi everyone, I'd like to make sure we're all on the same page with the plugin auto-version resolution stuff that we've been discussing lately (on the assembly-plugin vote thread, for one thing). I think it's clear that we cannot continue to allow Maven to resolve RELEASE or LATEST meta-versions for plugins any more. I'd actually argue that this is bad practice for ANY artifact that is to be resolved, including site skins, etc. since it kills our ability to deprecate features. Coming back to this topic. One of the good thing that we might lose is the fact that less people would test new releases. Regression would then take more time to get caught. Maybe there could be an easy way to let users use the latest ? maybe something like mvn -L ... ( L for latest) that would ignore all specified versions, without requiring a POM change ? Maybe too radical. Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-install-plugin :: Cannot override read-only parameter: artifactId ?
I can confirm that a download of the source from svn and building a snapshot locally does the trick. Please, oh, please, maven-lords that be! Please, deploy a new snapshot of 2.2 - the one on the snapshot site is almost a year old now. Thanx! jeff Jason Dillon wrote: Aighty I figured this out... the tag for maven-install-plugin-2.1 has groupId, artifactId, version, packaging and file all marked with '@readonly'. The latest trunk of maven-install-plugin does not have these tags. So, with 2.1 you can only `mvn install:install-file` from the command- line, and can not use the install-file goal from an execution. We need to get 2.2 released. * * * This worked for me before because I had built 2.2-SNAPSHOT locally (to test my forceVersion patch) and mvn decided to pick that up... not sure why though. Why would mvn pick up a locally built SNAPSHOT and use that instead of the released 2.1? I don't like the magical RELEASE stuff anyways... but I'd not expect that when a version for a plugin is omitted that mvn would pick up a non-release to use instead if it finds one in my repo cache. --jason On Apr 2, 2007, at 4:44 PM, Brett Porter wrote: I thought that had always been the case and was a known issue in the install plugin. On 03/04/2007, at 6:32 AM, Jason Dillon wrote: I all of a sudden started to see this today: snip [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Error configuring: org.apache.maven.plugins:maven-install- plugin. Reason: ERROR: Cannot override read-only parameter: artifactId in goal: install:install-file /snip From what I can tell this is using maven-install-plugin 2.1. Anyone know whats going on? I get the same problem with Maven 2.0.5 and 2.0.6 :-( --jason - 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] -- View this message in context: http://www.nabble.com/maven-install-plugin-%3A%3A-Cannot-override-read-only-parameter%3A-artifactId---tf3508089s177.html#a10263145 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
