RE: maven-idea-plugin
In a multi-module project you might be right that grouping by scope is not the
easiest way to group. However, we might consider creating groups for each
module and for each scope, i.e. in a project with three modules data, logic,
mvc. We might create the following list of project libraries:
- data-compile, data-runtime, data-test, etc.
- logic-compile, logic-runtime, etc
- mvc-compile, etc
- ${artifactId}-compile, etc.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
I don't agree with grouping by scope (that likely wouldn't work if I
understand correctly, as the project libraries would be different for
every module), but by groupId might as an optional configuration option.
Please put it in the JIRA.
- Brett
Roald Bankras wrote:
Hi all
Are there yet any plans to group the dependencies inside intellij?
I'd like to see some project libraries instead of module libraries. My
suggestion is to group them by scope, but another way might be to group them
by module (esspecially for multi module projects).
What are your idea's?
Roald Bankras
Software Engineer
JTeam b.v.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.6/339 - Release Date: 5/14/2006
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please make sources jar available to Maven1 users
I can't select Maven Project Administration in Jira create bug page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would I create a Jira Issue about Jira config ;-)
Nico.
Brett Porter a écrit :
Please put it in JIRA under the project MPA (Maven Project
Administration) - thanks.
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
group/artifact/artifact-xyz-java-sources.jar
So I can see three options :
1. Add a new Rule for java-sources :
RewriteRule
^([^/]+)/java-sources/([^0-9]+)-([0-9].+)-sources\.([^0-9]+)(\.md5|\.sha1){0,1}$
r/$1/$3/$4/$3-$4.$5$6 [PT]
2. Change the existing rules to ignore the java- prefix in
java-sources, something like this :
RewriteRule
^([^/]+)/(java-)?(jar|pom|config|distribution|source|dist|...
3. Update maven1 source-plugin to use sources as artifact type, and
also update IDE plugins (eclipse, idea...)
3-bis : change maven2 repo and pluins to use
artifact-xyz-java-sources.jar as sources jar
Please can any commiter take a look at this ?
Nico.
Nicolas De Loof a écrit :
Hello guys,
From a previous post I know Maven1 repo is a redirect to maven2
repository content, with path transcripted to match maven2 hierarchy.
commons-collection (as an example) has sources jar in maven2 repo
(http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1-sources.jar),
but I cannot get them using maven1 from
http://www.ibiblio.org/maven/commons-collections/java-sources/commons-collections-3.1-sources.jar
Maybe a new Apache rewrite rule may be required for this.
I would also be very interested if someone can give me the rewrite
rule used on ibiblio to convert m1 dependency path to m2 repo
hierarchy.
Nico.
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
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]
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please make sources jar available to Maven1 users
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select Maven Project Administration in Jira create bug page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would I create a Jira Issue about Jira config ;-)
Nico.
Brett Porter a écrit :
Please put it in JIRA under the project MPA (Maven Project
Administration) - thanks.
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
group/artifact/artifact-xyz-java-sources.jar
So I can see three options :
1. Add a new Rule for java-sources :
RewriteRule
^([^/]+)/java-sources/([^0-9]+)-([0-9].+)-sources\.([^0-9]+)(\.md5|\.sha1){0,1}$
r/$1/$3/$4/$3-$4.$5$6 [PT]
2. Change the existing rules to ignore the java- prefix in
java-sources, something like this :
RewriteRule
^([^/]+)/(java-)?(jar|pom|config|distribution|source|dist|...
3. Update maven1 source-plugin to use sources as artifact type, and
also update IDE plugins (eclipse, idea...)
3-bis : change maven2 repo and pluins to use
artifact-xyz-java-sources.jar as sources jar
Please can any commiter take a look at this ?
Nico.
Nicolas De Loof a écrit :
Hello guys,
From a previous post I know Maven1 repo is a redirect to maven2
repository content, with path transcripted to match maven2 hierarchy.
commons-collection (as an example) has sources jar in maven2 repo
(http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1-sources.jar),
but I cannot get them using maven1 from
http://www.ibiblio.org/maven/commons-collections/java-sources/commons-collections-3.1-sources.jar
Maybe a new Apache rewrite rule may be required for this.
I would also be very interested if someone can give me the rewrite
rule used on ibiblio to convert m1 dependency path to m2 repo
hierarchy.
Nico.
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
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]
This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive
this message in error, please notify the sender immediately and delete
all copies of this message.
-
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: Please make sources jar available to Maven1 users
Thanks a lot Emmanuel
Emmanuel Venisse a écrit :
http://jira.codehaus.org/browse/MPA-72
Emmanuel
Nicolas De Loof a écrit :
I can't select Maven Project Administration in Jira create bug
page :
http://jira.codehaus.org/secure/CreateIssue!default.jspa
BUT I can search for issues on this project... Is this a JIRA
configuration bug ? Would I create a Jira Issue about Jira config ;-)
Nico.
Brett Porter a écrit :
Please put it in JIRA under the project MPA (Maven Project
Administration) - thanks.
Nicolas De Loof wrote:
I've found it myself in maven SVN :
(maven/components/trunk/maven-meeper/src/bin/ibiblio-htaccess)
The current rewrite rule converts
group/java-sources/artifact-xyz-sources.jar
to
group/artifact/artifact-xyz-java-sources.jar
So I can see three options :
1. Add a new Rule for java-sources :
RewriteRule
^([^/]+)/java-sources/([^0-9]+)-([0-9].+)-sources\.([^0-9]+)(\.md5|\.sha1){0,1}$
r/$1/$3/$4/$3-$4.$5$6 [PT]
2. Change the existing rules to ignore the java- prefix in
java-sources, something like this :
RewriteRule
^([^/]+)/(java-)?(jar|pom|config|distribution|source|dist|...
3. Update maven1 source-plugin to use sources as artifact type,
and also update IDE plugins (eclipse, idea...)
3-bis : change maven2 repo and pluins to use
artifact-xyz-java-sources.jar as sources jar
Please can any commiter take a look at this ?
Nico.
Nicolas De Loof a écrit :
Hello guys,
From a previous post I know Maven1 repo is a redirect to maven2
repository content, with path transcripted to match maven2 hierarchy.
commons-collection (as an example) has sources jar in maven2 repo
(http://www.ibiblio.org/maven2/commons-collections/commons-collections/3.1/commons-collections-3.1-sources.jar),
but I cannot get them using maven1 from
http://www.ibiblio.org/maven/commons-collections/java-sources/commons-collections-3.1-sources.jar
Maybe a new Apache rewrite rule may be required for this.
I would also be very interested if someone can give me the rewrite
rule used on ibiblio to convert m1 dependency path to m2 repo
hierarchy.
Nico.
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are
not the intended recipient, you are not authorized to read,
print, retain, copy, disseminate, distribute, or use this message
or any part thereof. If you receive this message in error, please
notify the sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are
not the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
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]
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
-
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]
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin and Eclipse Plugin support
Rinku wrote:
Hi,
Not sure if there is some work in progress for Eclipse Plugin support
but here are some quick notes on the following logged in JIRA
http://jira.codehaus.org/browse/MECLIPSE-92
http://jira.codehaus.org/browse/MECLIPSE-103
1) Running eclipse:eclipse should generate the project definition just
as it does now, it detects if a org.eclipse.pde.PluginNature is
specified for .project and setups the PDE nature (updates to .classpath)
accordingly.
2) A Bundle Manifest writer could write out the Bundle Manifest. We
could default some of the headers to 'sensible' default values
(extracted from pom.xml), and allow for user to specify them via
configuration for the Eclipse plugin.
3) Plugin dependencies could be copied from the local M2 repo to under
Plugin/lib and Manifest updated for Bundle-Classpath values.
I thought I'd rake up a discussion :-)
As Cocoon 3.0 will be based on OSGi I need PDE support too. For the time being I
started with a branch of the maven-eclipse-plugin within the Cocoon SVN tree
(see
http://svn.apache.org/repos/asf/cocoon/trunk/tools/cocoon-maven-eclipse-plugin/).
The goal is providing a patch for the offical maven eclipse plugin within the
next weeks.
So far I added the configuration parameter pde. If set to true, the
PluginNature and the schema and manifest builders are added to .project.
Additionally, instead of pointing to libraries in the local repository, I copy
them to target/osgi/lib and point to them from within .classpath -
unfortunatly PDE doesn't allow referencing libraries outside of the project (as
you describe in 3).
Before I will provide a patch, I will implement what you describe in 2). I was
thinking of keeping Bundle-ClassPath in sync with the libraries in
target/osgi/lib.
What do you think?
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r406865 - /maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml
META-INT? [EMAIL PROTECTED] wrote: Author: epunzalan Date: Tue May 16 00:38:59 2006 New Revision: 406865 URL: http://svn.apache.org/viewcvs?rev=406865view=rev Log: MASSEMBLY-88 found the most probably cause for the continuum build failure... the capitalization of fileset Modified: maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml Modified: maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml URL: http://svn.apache.org/viewcvs/maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml?rev=406865r1=406864r2=406865view=diff == --- maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml (original) +++ maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml Tue May 16 00:38:59 2006 @@ -21,9 +21,9 @@ /formats fileSets fileSet - directorytarget/test-classes/FileSet/directory + directorytarget/test-classes/fileSet/directory includes -include**/components.xml/include +includeMETA-INT/plexus/components.xml/include /includes /fileSet /fileSets - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
doxia-renderer alpha 8 not on mergere repo
Just to double check if you guys are aware of this problem? mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere repo (=stopgap for repo1.maven.org being out due to codehaus.org disk failure). If plugin versions are locked down this means every build fails. It was mentioned somewhere in the user list deep down already, but it's unclear if someone will be so kind to upload doxia-renderer alpha 8? Thanks. -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: doxia-renderer alpha 8 not on mergere repo
yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/ Geoffrey De Smet wrote: Just to double check if you guys are aware of this problem? mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere repo (=stopgap for repo1.maven.org being out due to codehaus.org disk failure). If plugin versions are locked down this means every build fails. It was mentioned somewhere in the user list deep down already, but it's unclear if someone will be so kind to upload doxia-renderer alpha 8? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: doxia-renderer alpha 8 not on mergere repo
Just noticed (before your answer) I talked about the wrong pom: It's doxia-1.0-alpha-8 that isn't there. Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/doxia/doxia/1.0- alpha-8/doxia-1.0-alpha-8.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:doxia-site-renderer:jar:1.0-alpha-8 Reason: Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia -site-renderer:jar:1.0-alpha-8 With kind regards, Geoffrey De Smet Brett Porter wrote: yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/ Geoffrey De Smet wrote: Just to double check if you guys are aware of this problem? mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere repo (=stopgap for repo1.maven.org being out due to codehaus.org disk failure). If plugin versions are locked down this means every build fails. It was mentioned somewhere in the user list deep down already, but it's unclear if someone will be so kind to upload doxia-renderer alpha 8? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: doxia-renderer alpha 8 not on mergere repo
yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia/1.0-alpha-8/ Please: a) look first b) look at the messages on the users list that indicate what the real problem was. - Brett Geoffrey De Smet wrote: Just noticed (before your answer) I talked about the wrong pom: It's doxia-1.0-alpha-8 that isn't there. Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/doxia/doxia/1.0- alpha-8/doxia-1.0-alpha-8.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:doxia-site-renderer:jar:1.0-alpha-8 Reason: Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia -site-renderer:jar:1.0-alpha-8 With kind regards, Geoffrey De Smet Brett Porter wrote: yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/ Geoffrey De Smet wrote: Just to double check if you guys are aware of this problem? mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere repo (=stopgap for repo1.maven.org being out due to codehaus.org disk failure). If plugin versions are locked down this means every build fails. It was mentioned somewhere in the user list deep down already, but it's unclear if someone will be so kind to upload doxia-renderer alpha 8? Thanks. - 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-eclipse-plugin and Eclipse Plugin support
Hi Reinhard, Some notes inlined.. snip 1) Running eclipse:eclipse should generate the project definition just as it does now, it detects if a org.eclipse.pde.PluginNature is specified for .project and setups the PDE nature (updates to .classpath) accordingly. 2) A Bundle Manifest writer could write out the Bundle Manifest. We could default some of the headers to 'sensible' default values (extracted from pom.xml), and allow for user to specify them via configuration for the Eclipse plugin. 3) Plugin dependencies could be copied from the local M2 repo to under Plugin/lib and Manifest updated for Bundle-Classpath values. I thought I'd rake up a discussion :-) As Cocoon 3.0 will be based on OSGi I need PDE support too. For the time being I started with a branch of the maven-eclipse-plugin within the Cocoon SVN tree (see http://svn.apache.org/repos/asf/cocoon/trunk/tools/cocoon-maven-eclipse-plugin/). The goal is providing a patch for the offical maven eclipse plugin within the next weeks. So far I added the configuration parameter pde. If set to true, the PluginNature and the schema and manifest builders are added to .project. I have a patch submitted for this for the maven-eclipse-plugin. Though not sure when that gets integrated into the plugin. IMHO you would not need a separate config param but just detect the natures being specified in the config and that should set up PDE project definition. Additionally, instead of pointing to libraries in the local repository, I copy them to target/osgi/lib and point to them from within .classpath - unfortunatly PDE doesn't allow referencing libraries outside of the project (as you describe in 3). Yep, I noticed that too. Just curious why do want to copy them to the target/osgi/lib and then reference them from there. Why not copy them under the PDE project/osgi/lib directory (and may be add that folder to ignore list in for CVS/SVN). I think you will need to update both .classpath and Manifest.mf (see 3) for the libs. Before I will provide a patch, I will implement what you describe in 2). I was thinking of keeping Bundle-ClassPath in sync with the libraries in target/osgi/lib. You can also look under Apache Felix sources, they have a maven osgi plugin implemented, may be you can draw some ideas from there as well. What do you think? /snip Cheers, Rahul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: doxia-renderer alpha 8 not on mergere repo
Brett, My apologies, I must look first indeed and tell you about the real problem, instead of start geussing. It's just I had it today and yesterday on my work computer, saw users complaining on the user list and also got a mail from a couple people from spring-richclient. I cannot reproduce it on my home computer (did mvn -U site before codehaus was down). If I still have it tommorrow on my work computer, I 'll find out the cause and provide a decent report as I should have done in the first place. With kind regards, Geoffrey De Smet Brett Porter wrote: yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia/1.0-alpha-8/ Please: a) look first b) look at the messages on the users list that indicate what the real problem was. - Brett Geoffrey De Smet wrote: Just noticed (before your answer) I talked about the wrong pom: It's doxia-1.0-alpha-8 that isn't there. Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/doxia/doxia/1.0- alpha-8/doxia-1.0-alpha-8.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:doxia-site-renderer:jar:1.0-alpha-8 Reason: Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia -site-renderer:jar:1.0-alpha-8 With kind regards, Geoffrey De Smet Brett Porter wrote: yes, it is: http://repo.mergere.com/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/ Geoffrey De Smet wrote: Just to double check if you guys are aware of this problem? mvn -U site = build-fails because doxia-renderer alpha 8 not on mergere repo (=stopgap for repo1.maven.org being out due to codehaus.org disk failure). If plugin versions are locked down this means every build fails. It was mentioned somewhere in the user list deep down already, but it's unclear if someone will be so kind to upload doxia-renderer alpha 8? Thanks. - 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]
https://svn.codehaus.org down all day...
Any ETA? I haven't seen any status emails like I did with the Apache problems. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin and Eclipse Plugin support
Rinku wrote:
snip/
So far I added the configuration parameter pde. If set to true, the
PluginNature and the schema and manifest builders are added to .project.
I have a patch submitted for this for the maven-eclipse-plugin. Though
not sure when that gets integrated into the plugin. IMHO you would not
need a separate config param but just detect the natures being specified
in the config and that should set up PDE project definition.
My idea was consistency with the WTP configuration parameter, less typing and
I'm sure that I will never remember the class name of the nature ;-)
Additionally, instead of pointing to libraries in the local
repository, I copy them to target/osgi/lib and point to them from
within .classpath - unfortunatly PDE doesn't allow referencing
libraries outside of the project (as you describe in 3).
Yep, I noticed that too. Just curious why do want to copy them to the
target/osgi/lib and then reference them from there. Why not copy them
under the PDE project/osgi/lib directory (and may be add that folder to
ignore list in for CVS/SVN).
My initial idea was that a mvn clean should remove them. But I'm not sure
about this.
I think you will need to update both
.classpath and Manifest.mf (see 3) for the libs.
Yes, the cocoon-maven-eclipse-plugin already does so.
Before I will provide a patch, I will implement what you describe in
2). I was thinking of keeping Bundle-ClassPath in sync with the
libraries in target/osgi/lib.
You can also look under Apache Felix sources, they have a maven osgi
plugin implemented, may be you can draw some ideas from there as well.
Thanks for the pointer!
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: javasvn license
FYI seems that we won't be able of having a java implementation of svn. In fact I think we have to remove it from apache -- Forwarded message -- From: Justin Erenkrantz [EMAIL PROTECTED] Date: May 16, 2006 12:28 PM Subject: Re: javasvn license To: Mario Ivankovits [EMAIL PROTECTED] Cc: legal-discuss@apache.org On 5/16/06, Mario Ivankovits [EMAIL PROTECTED] wrote: I would like to know if the JavaSVN license [1] if compatible with ASF so that I can add it as dependency for the jakarta commons VFS project. No - it's a Category X in Cliff's policy. It requires source distribution of changes (clause 3). -- justin - DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See http://www.apache.org/licenses/ for official ASF policies and documents. - 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]
Re: javasvn license
Is that really the only problem with the license? Since noone would be making changes to the source, does that condition apply at all? On 5/17/06, Carlos Sanchez [EMAIL PROTECTED] wrote: FYI seems that we won't be able of having a java implementation of svn. In fact I think we have to remove it from apache -- Forwarded message -- From: Justin Erenkrantz [EMAIL PROTECTED] Date: May 16, 2006 12:28 PM Subject: Re: javasvn license To: Mario Ivankovits [EMAIL PROTECTED] Cc: legal-discuss@apache.org On 5/16/06, Mario Ivankovits [EMAIL PROTECTED] wrote: I would like to know if the JavaSVN license [1] if compatible with ASF so that I can add it as dependency for the jakarta commons VFS project. No - it's a Category X in Cliff's policy. It requires source distribution of changes (clause 3). -- justin - DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See http://www.apache.org/licenses/ for official ASF policies and documents. - 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] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
RE: javasvn license
Where is the license problem? With JavaSVN or SVN? According to tigris.org, svn is using an apache compatible license. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, May 16, 2006 2:47 PM To: Maven Developers List Subject: Fwd: javasvn license FYI seems that we won't be able of having a java implementation of svn. In fact I think we have to remove it from apache -- Forwarded message -- From: Justin Erenkrantz [EMAIL PROTECTED] Date: May 16, 2006 12:28 PM Subject: Re: javasvn license To: Mario Ivankovits [EMAIL PROTECTED] Cc: legal-discuss@apache.org On 5/16/06, Mario Ivankovits [EMAIL PROTECTED] wrote: I would like to know if the JavaSVN license [1] if compatible with ASF so that I can add it as dependency for the jakarta commons VFS project. No - it's a Category X in Cliff's policy. It requires source distribution of changes (clause 3). -- justin - DISCLAIMER: Discussions on this list are informational and educational only. Statements made on this list are not privileged, do not constitute legal advice, and do not necessarily reflect the opinions and policies of the ASF. See http://www.apache.org/licenses/ for official ASF policies and documents. - 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]
Re: javasvn license
Where is the license problem? With JavaSVN or SVN? According to tigris.org, svn is using an apache compatible license. Maybe they are not aware that it is not? Maybe this can be resolved by talking to them ...so they might fix that. cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: javasvn license
Either way if they give you guys trouble you can try sending chuck norris in ;) (sorry, just loved that signature..heh) On 5/16/06, Torsten Curdt [EMAIL PROTECTED] wrote: Where is the license problem? With JavaSVN or SVN? According to tigris.org, svn is using an apache compatible license. Maybe they are not aware that it is not? Maybe this can be resolved by talking to them ...so they might fix that. cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
Re: javasvn license
tmatesoft JavaSVN is the problem, not SVN per se http://tmate.org/svn/licensing/index.html Please join legal discussion if you want to discuss the legal terms, but as I understand it's pretty clear. It's similar case as GPL, where apache software can't depend on it, no matter if we just use it. On 5/16/06, Torsten Curdt [EMAIL PROTECTED] wrote: Where is the license problem? With JavaSVN or SVN? According to tigris.org, svn is using an apache compatible license. Maybe they are not aware that it is not? Maybe this can be resolved by talking to them ...so they might fix that. cheers -- Torsten - 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]
Re: javasvn license
On 5/17/06, Carlos Sanchez [EMAIL PROTECTED] wrote: tmatesoft JavaSVN is the problem, not SVN per se http://tmate.org/svn/licensing/index.html Ah, thought the previous post was referring to JavaSVN. Maybe still worth talking to them. Please join legal discussion if you want to discuss the legal terms, but as I understand it's pretty clear. It's similar case as GPL, where apache software can't depend on it, no matter if we just use it. I am on legal ...responded to the wrong list, sorry cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What is filtered in assembly's FileItem
Hello, I am trying to fix http://jira.codehaus.org/browse/MASSEMBLY-100 and having trouble understanding the purpose of filtered element in FileItem if the descriptor. Could someone or the owner of that feature explains what it really means? Thanks -Dan
Re: svn commit: r406865 - /maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml
hmmm... you're right. Seems like assembly is excluding all META-INF/plexus/components.xml and creating/adding the temp file for it even if the file is NOT in include and/or is excluded. This IS a bug. I'll create a jira issue for this Brett Porter wrote: META-INT? [EMAIL PROTECTED] wrote: Author: epunzalan Date: Tue May 16 00:38:59 2006 New Revision: 406865 URL: http://svn.apache.org/viewcvs?rev=406865view=rev Log: MASSEMBLY-88 found the most probably cause for the continuum build failure... the capitalization of fileset Modified: maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml Modified: maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml URL: http://svn.apache.org/viewcvs/maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml?rev=406865r1=406864r2=406865view=diff == --- maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml (original) +++ maven/plugins/trunk/maven-assembly-plugin/src/test/resources/assemblies/plexus-components.xml Tue May 16 00:38:59 2006 @@ -21,9 +21,9 @@ /formats fileSets fileSet - directorytarget/test-classes/FileSet/directory + directorytarget/test-classes/fileSet/directory includes -include**/components.xml/include +includeMETA-INT/plexus/components.xml/include /includes /fileSet /fileSets - 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: What is filtered in assembly's FileItem
Hi Dan, It is like the filtering of resources where the expression in resource files such as LICENSE.txt can be interpolated. Hope this helps, allan dan tran wrote: Hello, I am trying to fix http://jira.codehaus.org/browse/MASSEMBLY-100 and having trouble understanding the purpose of filtered element in FileItem if the descriptor. Could someone or the owner of that feature explains what it really means? Thanks -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is filtered in assembly's FileItem
when filtered is true, it means expressions like
${project.build.directory} inside the file is replaced with the actual
value when used in your pom.xml
dan tran wrote:
Hello, I am trying to fix
http://jira.codehaus.org/browse/MASSEMBLY-100 and
having trouble
understanding the purpose of filtered element in FileItem if the
descriptor.
Could someone or the owner of that feature explains what it really means?
Thanks
-Dan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
