You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2005/01/13 14:02:27 UTC
[jira] Created: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Thu, 13 Jan 2005 8:00 AM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Nils-Helge Garli
Created: Thu, 27 Jan 2005 3:02 PM
Body:
For instance, in our current project, we need to have an external folder with some property files in the classpath. In Eclipse 2.1, one would solve this by adding a environment variable that points to this folder, and add it to the build path of the project. We could solve this by copying the required property files into the project source folder, but this is not what we want, as it can be multiple property files, and they are shared between projects.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29340
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Thu, 27 Jan 2005 3:02 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Nils-Helge Garli
Created: Thu, 27 Jan 2005 5:20 PM
Body:
Yes, and we do that already for project local properties that reside in a project relative folder. But this is for system wide property files in folders that are referred to with eclipse classpath variables which are outside the project.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29349
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Thu, 27 Jan 2005 5:20 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 27 Jan 2005 4:13 PM
Body:
This is what we use:
maven.eclipse.classpath.include=src/conf,src/test-resources
That adds the src/conf and src/test-resources to the classpath and then everything works!
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29348
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Thu, 27 Jan 2005 4:13 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Nils-Helge Garli
Created: Fri, 28 Jan 2005 2:12 PM
Body:
I do realise that it might sound a bit out of scope of a maven-plugin, but reality is that we cannot use the eclipse goals if this is not implemented, as we would have to manually add this after every run.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29378
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Fri, 28 Jan 2005 2:12 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Nils-Helge Garli
Created: Fri, 28 Jan 2005 1:33 PM
Body:
They don't. It's only inside eclipse for integration test clients that we run manually. So it's only relevant for setting up the eclipse project correctly, not for building the project with maven.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29377
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Fri, 28 Jan 2005 1:33 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 27 Jan 2005 2:34 PM
Body:
Can you provide more detail on what you are trying to accomplish? What would be a use case for more variables?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29338
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Thu, 27 Jan 2005 2:34 PM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MPECLIPSE-66) Custom eclipse variables in .classpath generation
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Fri, 28 Jan 2005 10:40 AM
Body:
Okay.. I see, so you are pulling in system wide property files. Now, my question is, how (if you aren't using Eclipse, but instead using Maven) and running goals like maven test or jar, how do those property files get pulled into the classpath?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-66?page=comments#action_29364
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-66
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-66
Summary: Custom eclipse variables in .classpath generation
Type: New Feature
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Nils-Helge Garli
Created: Thu, 13 Jan 2005 8:00 AM
Updated: Fri, 28 Jan 2005 10:40 AM
Environment: WSAD 5.1.2, maven 1.0.2
Description:
I miss a feature to be able to add custom Eclipse environment variables to the .classpath file. The maven.eclipse.classpath.include property only works with source directories that are relative to the project root, and cannot be used for this puprpose. Maybe a new maven.eclipse.classpath.variable would solve this.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org