[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Max Rydahl Andersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen commented on JBIDE-4706:
--------------------------------------------
Yes, I understand the issue is not fully solved - but part of it is fixed in JBIDE-4632.
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-4706
> URL: https://jira.jboss.org/jira/browse/JBIDE-4706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Fix For: 3.1.0.M3
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
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
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-4680) add conf-relative paths for default filesets
by Rob Stryker (JIRA)
add conf-relative paths for default filesets
--------------------------------------------
Key: JBIDE-4680
URL: https://jira.jboss.org/jira/browse/JBIDE-4680
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 3.1.0.M2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.1.0.M3
Currently, relative paths are based on the getLocation() method of the runtime. For JBoss servers, this means a relative path should be something like server/default/deploy.
The problem here is that the user may want to set up a default fileset relative to the concrete configuration of that server's runtime.
Allow default filesets for jboss servers to have a relative path of {config}/conf/jboss-log4j.xml. This path can be translated to server/all/conf/jboss-log4j.xml when being added to the new server as a fileset.
--
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
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-3451) VPE - Preferences - please remove or rename "Default Editor Tab"
by Vitali Yemialyanchyk (JIRA)
VPE - Preferences - please remove or rename "Default Editor Tab"
----------------------------------------------------------------
Key: JBIDE-3451
URL: https://jira.jboss.org/jira/browse/JBIDE-3451
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.0.0.cr1
Reporter: Vitali Yemialyanchyk
Assignee: Maxim Areshkau
Priority: Minor
Maxim, as you told me "Default Editor Tab" selection means default editor tab selection for new created jsp file (for example), in other rest cases vpe remember it's last open state. When i press "Preferences" and "Default Editor Tab" i expect to change something usefull for current editor.
We can easy remove it and always open "Visual/Source" for new created files.
Or it should be renamed into something like this "Default Editor Tab for new VPE files" - this name help you avoid questions.
--
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
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-4249) Update of dependent archives
by Ondrej Medek (JIRA)
Update of dependent archives
----------------------------
Key: JBIDE-4249
URL: https://jira.jboss.org/jira/browse/JBIDE-4249
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.0.GA
Environment: Win XP, Eclipse 3.4.2 Build id: M20090211-1700
Reporter: Ondrej Medek
Priority: Minor
I have a two archives, one is x.jar (compressed) and x.ear (exploded). x.ear contains a fileset, which includes x.jar. So my directory structure is:
x.jar
ear/x.ear/
ear/x.ear/x.jar
x.jar contains compiled Java classes. When I make a change in the Java code, the x.jar is properly updated, however, the x.ear contains the old version of x.jar. I have to select "Build Archive" action from the menu.
--
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
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-4575) Nested archives are not updated when the respective files change in the workspace
by Flavio Costa (JIRA)
Nested archives are not updated when the respective files change in the workspace
---------------------------------------------------------------------------------
Key: JBIDE-4575
URL: https://jira.jboss.org/jira/browse/JBIDE-4575
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 3.0.1.GA
Environment: Linux mobile 2.6.30-ARCH #1 SMP PREEMPT Fri Jun 19 21:25:17 UTC 2009 i686 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel GNU/Linux
Eclipse 3.4.2
JBoss Application Server 4.2.3.GA
Reporter: Flavio Costa
Fix For: 3.0.2.GA
I'm currently experiecing some very strange.
As I explained to Max on IRC couple days ago, I have that has a structure pretty much similar to what seam-gen generates (I've actually generated it through seam-gen and then modified some bits here and there) and I'm using Project Archives in order to have, mainly, fast redeploys of view artifacts (XHTMLs, CSS, JS, ...) and a better integration with IDE (publishing to the server inside eclipse, for example).
Let's say the project is called "BugSample" in my workspace.
Inside /BugSample/resources/META-INF there's an "application.xml" which is copied to /BugSample/build-artifacts/project-archives/BugSample.ear/META-INF. That's perfecly correct and as soon as I change /BugSample/resources/META-INF/application.xml, Project Archives "notices" that change and copy it to the correct directory and, as the application is published to the server and I have changed the application descriptor, the app is then redeployed. That is the proof that Project Archives is enabled and "should" be working.
But my application is also composed by EJBs and some other POJOs and a view layer, so I must have, nested to the EAR, a JAR and a WAR. That's where the problem comes in.
The JAR and the WAR were created "inside the EAR" (the attached image shows that). All my view stuff (XHTML, CSS,...) are inside /BugSample/view and are mapped in Project Archives to be copied to /BugSample/build-artifacts/project-archives/BugSample.ear/BugSample.war/. I guessed that whenever I change the content of any file inside /BugSample/view the WAR generated by Project Archives would be updated right way, the same way the application.xml affected the EAR archive. The same happens for the JAR.
The project I'm having problem is available for download here:
http://dcc.ufrj.br/~coutinho/jbtools/FenixTemplate.tar.bz2
Just extract it and import the project in Eclipse.
If you need anymore info I'll be more than happy to provide.
--
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
14 years, 9 months
[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Alexander Lengson (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Alexander Lengson commented on JBIDE-4706:
------------------------------------------
>Moved to right project, set component and fix versions and now mentioning that this is related to JBIDE-4632 (i believe).
Max,
this issue partly related to JBIDE-4632 . That part is not the question now.
There are three other issues described more detailed in comments.
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-4706
> URL: https://jira.jboss.org/jira/browse/JBIDE-4706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Fix For: 3.1.0.M3
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
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
14 years, 9 months
[JBoss JIRA] Updated: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Max Rydahl Andersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ]
Max Rydahl Andersen updated JBIDE-4706:
---------------------------------------
Component/s: maven
Fix Version/s: 3.1.0.M3
Moved to right project, set component and fix versions and now mentioning that this is related to JBIDE-4632 (i believe).
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-4706
> URL: https://jira.jboss.org/jira/browse/JBIDE-4706
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Fix For: 3.1.0.M3
>
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
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
14 years, 9 months