[JBoss JIRA] Created: (JBIDE-2516) build path' referenced libraries not included in war
by arne anka (JIRA)
build path' referenced libraries not included in war
----------------------------------------------------
Key: JBIDE-2516
URL: http://jira.jboss.com/jira/browse/JBIDE-2516
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 2.0.1
Environment: eclipse 3.3.2, jboss tool 2.0.1.GA (dunno why it's not listed above)
Reporter: arne anka
creating a war in archive view (why no entry in context menu? that view is not really intuitive) results in a war not deployable -- jboss complains over not being able to create smth.
further research shows that libraries referenced in the build path (and _not_ physically located in WEB-INF/libs/) are _not_ included while creating the war.
deploying the application from the jboss ide includes those libs, though -- but for productive use the app needs to be packed as war and thus include even libs only referenced ...
a workaround might be to create a fileset by hand -- but because those libs are spread over several places it's a rather tedious task.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Vitali Yemialyanchyk (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ]
Vitali Yemialyanchyk commented on JBIDE-719:
--------------------------------------------
I didn't find a sense to add DTP support for core and annotations modes - cause there is configuration file - why we should multiply configuration ways without essential usability results? What benefits will get the user from such support? I can't imagine the situation.
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: https://jira.jboss.org/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: 719.rar, EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Dima Geraskov (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ]
Dima Geraskov commented on JBIDE-719:
-------------------------------------
> 1)JPA projects seem to be the only one having DTP support ....not sure why that limtation is there?
Yes, as I see in code only JPA-based console configurations knows how to work with DTP connecion profile.
See ConsoleConfiguration#buildJPAConfiguration(...).
I don't know why it wasn't been added to other console configuration modes(core and annotations).
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: https://jira.jboss.org/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: 719.rar, EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Dima Geraskov (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ]
Dima Geraskov updated JBIDE-719:
--------------------------------
Attachment: 719.rar
The problem occured when db driver class was not loaded before by other console configuration. Moved calculation of dialect after registration of neew driver in ConsoleConfiguration class.
See ConsoleConfiguration #buildWith(final Configuration cfg, final boolean includeMappings)
Line 256.
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: https://jira.jboss.org/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: 719.rar, EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[JBoss JIRA] Commented: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection
by Max Rydahl Andersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-719?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen commented on JBIDE-719:
-------------------------------------------
Status update:
I tried to apply this with the old patch (before Dimas comment on the 28th)
Found two things:
1) JPA projects seem to be the only one having DTP support ....not sure why that limtation is there?
2) I couldn't get any basic JPA project to work - not sure if that is the patch or some other new regression bug.
> Hibernate Tools should be able to use a named Eclipse provided connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-719
> URL: https://jira.jboss.org/jira/browse/JBIDE-719
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 3.0.0.beta1
>
> Attachments: 719.zip, EditConsolleConfig.JPG, EditConsolleConfig_Res1.jpg, EditConsolleConfig_Res2.jpg, EditConsolleConfigNew2.JPG, JBIDE-719.zip, NewSeamProj.JPG
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml
> Users should be able to say to use a named WTP provided database connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months