[jira] [Commented] (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2012-01-23 Thread GK Ephorus (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13190959#comment-13190959
 ] 

GK Ephorus commented on IVYDE-227:
--

I presume this makes IVYDE-290 related? (Looking forward to seeing how I 
configure me Ivy projects as Java EE Utility project) If so, we can close 
that, too.

 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2012-01-13 Thread Tom Mack (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185739#comment-13185739
 ] 

Tom Mack commented on IVYDE-227:


I was able to get past this by recreating the dependent project as a Java EE 
Utility Project.

 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2012-01-13 Thread Matt Benson (Commented) (JIRA)

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13185755#comment-13185755
 ] 

Matt Benson commented on IVYDE-227:
---

Tom, please confirm:  you say that having the workspace-resolved project 
configured in Eclipse as a Java EE Utility project causes WTP to properly add 
it to a deployed webapp from an Ivy library?  With which Eclipse/WTP versions 
have you confirmed this behavior?

Thanks,
Matt

 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2010-06-02 Thread JIRA

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874469#action_12874469
 ] 

Thorbjørn Ravn Andersen commented on IVYDE-227:
---

Could you please add to the FAQ and 
http://ant.apache.org/ivy/ivyde/history/latest-milestone/cpc/wtp.html that 
there is a known issue with WTP and Resolve in workspace?

Additionally if there is a way to work around this which can be used by 
newcomers to Ivy so the functionality can be useful anyway, I would appreciate 
hearing about it.Basically I want to have Ivy resolve which customer 
specific library to add to a web app while developing the customer specific 
library so the deployment mechanism should not be too heavy.

 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2010-01-09 Thread JIRA

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798338#action_12798338
 ] 

Nicolas Lalevée commented on IVYDE-227:
---

I don't know how much can do IvyDE about it, as it just uses the JDT API. And 
then WTP use the JDT API to get the classpath build by IvyDE.
You should probably better open an entry in WTP's bugzilla. If you do it it 
would be cool if you could keep us posted as this issue was discussed several 
times:
http://old.nabble.com/-IvyDE--resolve-in-workspace-WTP-td24223638.html


 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (IVYDE-227) WTP Resolve Project in Workspace does not get exported to wtpwebapps directory

2010-01-09 Thread Matt Benson (JIRA)

[ 
https://issues.apache.org/jira/browse/IVYDE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798376#action_12798376
 ] 

Matt Benson commented on IVYDE-227:
---

There already is such an issue; please vote for it:  
https://bugs.eclipse.org/bugs/show_bug.cgi?id=184125 (I never noticed this JIRA 
issue or I should already have shared this information).  Really there's no 
reason to keep this JIRA issue open, except as it might make it easier to find 
when we have to continually draw folks' attention back to this missing 
feature of WTP.

 WTP Resolve Project in Workspace does not get exported to wtpwebapps 
 directory
 

 Key: IVYDE-227
 URL: https://issues.apache.org/jira/browse/IVYDE-227
 Project: IvyDE
  Issue Type: Bug
Affects Versions: 2.1.0
 Environment: Windows
 Eclipse Galileo WTP
Reporter: Dave

 Selecting Resolve in workspace correctly resolves the project in the 
 workspace, but the project's jar is not exported to the output directory.  
 Runtime ClassNotFoundExceptions occur unless the user manually adds project 
 as Java EE dependency

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.