[jira] Created: (MPIDEA-35) Patch for .iml template for Irida (Idea 5)
Patch for .iml template for Irida (Idea 5)
--
Key: MPIDEA-35
URL: http://jira.codehaus.org/browse/MPIDEA-35
Project: maven-idea-plugin
Type: Bug
Versions: 1.5
Environment: Irida (Idea 5)
Reporter: Otto von Wachter
Fix For: 1.5
Attachments: module.jelly.patch
The problem is that maven generated .iml files don't specify module type, so
Idea gives a warning and doesn't allow to see module properties in the project
properties window.
The solution: (patch to maven-idea-plugin-1.5\plugin-resources\templates\v4)
*** module.jelly.bak Fri Jun 25 13:13:36 2004
--- module.jelly Thu Jun 23 10:17:20 2005
***
*** 22,33
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:if test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:if
! j:if test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:if
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--- 22,38
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:choose
! j:when test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:when
! j:when test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:when
! j:otherwise
! j:set var=IDEA_TYPE value=JAVA_MODULE/
! /j:otherwise
! /j:choose
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPIDEA-35) Patch for .iml template for Irida (Idea 5)
[ http://jira.codehaus.org/browse/MPIDEA-35?page=all ]
Otto von Wachter updated MPIDEA-35:
---
Attachment: module.jelly.patch
Ok, sorry, here is the unified diff attached
Patch for .iml template for Irida (Idea 5)
--
Key: MPIDEA-35
URL: http://jira.codehaus.org/browse/MPIDEA-35
Project: maven-idea-plugin
Type: Bug
Versions: 1.5
Environment: Irida (Idea 5)
Reporter: Otto von Wachter
Fix For: 1.5
Attachments: module.jelly.patch, module.jelly.patch, module.jelly.patch2
The problem is that maven generated .iml files don't specify module type, so
Idea gives a warning and doesn't allow to see module properties in the
project properties window.
The solution: (patch to maven-idea-plugin-1.5\plugin-resources\templates\v4)
*** module.jelly.bak Fri Jun 25 13:13:36 2004
--- module.jelly Thu Jun 23 10:17:20 2005
***
*** 22,33
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:if test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:if
! j:if test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:if
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--- 22,38
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:choose
! j:when test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:when
! j:when test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:when
! j:otherwise
! j:set var=IDEA_TYPE value=JAVA_MODULE/
! /j:otherwise
! /j:choose
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPIDEA-35) Patch for .iml template for Irida (Idea 5)
[ http://jira.codehaus.org/browse/MPIDEA-35?page=all ]
Otto von Wachter updated MPIDEA-35:
---
Attachment: module.jelly.patch2
ok, sorry, here is the unified diff attached
Patch for .iml template for Irida (Idea 5)
--
Key: MPIDEA-35
URL: http://jira.codehaus.org/browse/MPIDEA-35
Project: maven-idea-plugin
Type: Bug
Versions: 1.5
Environment: Irida (Idea 5)
Reporter: Otto von Wachter
Fix For: 1.5
Attachments: module.jelly.patch, module.jelly.patch, module.jelly.patch2
The problem is that maven generated .iml files don't specify module type, so
Idea gives a warning and doesn't allow to see module properties in the
project properties window.
The solution: (patch to maven-idea-plugin-1.5\plugin-resources\templates\v4)
*** module.jelly.bak Fri Jun 25 13:13:36 2004
--- module.jelly Thu Jun 23 10:17:20 2005
***
*** 22,33
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:if test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:if
! j:if test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:if
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--- 22,38
maven:get var=type plugin=maven-multiproject-plugin
property=maven.multiproject.type /
j:set var=IDEA_TYPE value=/
! j:choose
! j:when test=${type == 'ejb'}
j:set var=IDEA_TYPE value=J2EE_EJB_MODULE/
! /j:when
! j:when test=${type == 'war'}
j:set var=IDEA_TYPE value=J2EE_WEB_MODULE/
! /j:when
! j:otherwise
! j:set var=IDEA_TYPE value=JAVA_MODULE/
! /j:otherwise
! /j:choose
module version=4 relativePaths=false type=${IDEA_TYPE}
j:if test=${type == 'ejb'}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPSTRUTS-1) taskdef class org.apache.maven.struts.Struts10WarValidator cannot be found
[ http://jira.codehaus.org/browse/MPSTRUTS-1?page=comments#action_41349 ] Otto von Wachter commented on MPSTRUTS-1: - Anyone know how to fix this at least? Would love to get this working.. taskdef class org.apache.maven.struts.Struts10WarValidator cannot be found -- Key: MPSTRUTS-1 URL: http://jira.codehaus.org/browse/MPSTRUTS-1 Project: maven-struts-plugin Type: Bug Components: default Environment: Windows XP, Maven 1.0, Java 1.4.2., Eclipse 3.0 Reporter: Ricardo Gladwell I've set the struts goal as a post-goal for the war:war goal. However, build always fails with: BUILD FAILED File.. C:\Documents and Settings\rglad\.maven\cache\maven-struts-plugin-1.3\plugin.jelly Element... taskdef Line.. 32 Column 71 taskdef class org.apache.maven.struts.Struts10WarValidator cannot be found -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: private jar dependencies
Thanks for these two+ suggestions on how to work with
private jars.
While I can't contribute much on the implementation
details, I have some thoughts on the big picture.
You can tell someone that setting up an artifact repository
is the right way to do it, but regardless Maven/Ant users
will use whatever approach makes their life easier
(whatever solution is most appropriate for a given
situation).
In my case I want to use some of the features of Maven
(reports, web site, etc.) but don't need all of them. I
probably won't set up an artifact repository until the
incremental benefit of doing so outweighs the incremental
cost (complexity, time--remember setting up a repository
also involves maintaining, training, backing up, etc.) So
I don't think it should be an all-or-nothing choice.
Regards,
Otto
--- Jason van Zyl [EMAIL PROTECTED] wrote:
On Fri, 2003-06-20 at 18:55, Otto von Wachter wrote:
Hi all,
I have a question/suggestion on jar dependencies. I
think
maven is perfect for open source (large/collaborative)
projects. I would like to leverage Maven for my
internal
project at work, but not all dependencies are available
on
ibiblio (some are not open source, etc.) Also it makes
sense for us to keep these jars in CVS, to make sure
they
don't get lost, and just because it works.
What I would like is to specify some private jar
dependencies that are stored in a lib dir. Is there a
quick
hack that would allow me to do this? If it is, perhaps
documenting it would increase the adoption of maven
among
users like me. If not would it be easy to add this
feature?
I was thinking of something like this:
privateDependencies
libDirectorylib/libDirectory
/privateDependencies
or maybe
build
baseClasspath
fileset dir=lib
include name=*.jar/
/fileset
/baseClasspath
...
/build
I know this might go against the maven philosophy,
but it
would be optional, and it's one of the things that is
keeping me from using Maven instead of Ant.
Something for this will never be built into Maven. You
lose anything
Maven provides in the way of auto-downloading and
verification. I would
recommend you save yourself much grief and spend 10
minutes and make
yourself a local repository. But do what you like, here's
one way you
might do it:
project
xmlns:ant=jelly:ant
xmlns:maven=jelly:maven
preGoal name=java:compile
ant:path id=my.doublebarrel.classpath
fileset dir=${basedir}/lib
include name=**/*.jar/
/fileset
/ant:path
maven:addPath
id=maven.dependency.classpath
refid=my.doublebarrel.classpath/
/preGoal
/project
Again, I do not recommend you do this.
Otto
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a
rational
and technical order to justify his work and to be
justified in it.
-- Jacques Ellul, The Technological Society
-
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]
private jar dependencies
Hi all, I have a question/suggestion on jar dependencies. I think maven is perfect for open source (large/collaborative) projects. I would like to leverage Maven for my internal project at work, but not all dependencies are available on ibiblio (some are not open source, etc.) Also it makes sense for us to keep these jars in CVS, to make sure they don't get lost, and just because it works. What I would like is to specify some private jar dependencies that are stored in a lib dir. Is there a quick hack that would allow me to do this? If it is, perhaps documenting it would increase the adoption of maven among users like me. If not would it be easy to add this feature? I was thinking of something like this: privateDependencies libDirectorylib/libDirectory /privateDependencies or maybe build baseClasspath fileset dir=lib include name=*.jar/ /fileset /baseClasspath ... /build I know this might go against the maven philosophy, but it would be optional, and it's one of the things that is keeping me from using Maven instead of Ant. Otto - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
