[JBoss JIRA] (JBIDE-18508) EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18508?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-18508:
---------------------------------------
[~jeffmaury] This issue is not fixed, I have tried it in DevStudio (Version: 10.3.0.GA, Build id: GA-v20170216-0823-B7105) with EAP 6.2 and 6.4.
Workaround is working.
Note:
In project restbay-ear in file jboss-seam-restbay-ds.xml must be changed line 2 from:
{code:java}
<datasources xmlns="http://www.jboss.org/ironjacamar/schema">
{code}
to
{code:java}
<datasources xmlns="http://www.jboss.org/doc/schema">
{code}
(from http://tools.jboss.org/blog/2014-04-27-referenced-file-contains-errors-fo...)
> EAR Maven project loses lib/ artifacts deployed to EAP broken after closing/reopening
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18508
> URL: https://issues.jboss.org/browse/JBIDE-18508
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.1.2.Final
> Reporter: Marek Schmidt
> Assignee: Fred Bricon
> Labels: f2f2014
> Fix For: LATER
>
> Attachments: seam-restbay-src.zip
>
>
> EAR Maven project loses lib/ artifacts deployed to EAP after closing/reopening
> 0. setup the redhat techpreview/all maven repository
> 1. Import the (attached) project as Maven project
> 2. Deploy the restbay-ear project to EAP 6.2 (or 6.3)
> 3. Close all 4 subprojects of the restbay project
> 4. reopen all the restbay projects
> 5. now the application will automatically redeploy
> 6. this redeployment will result in a failure.
> If you compare the deployment folders before/after the closing/reopening of the project, you will notice some of the restbay-ear.ear/lib/ libraries are missing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-1045) Droold plugin version doesn't match the appropriate bundle version
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1045:
----------------------------------------
Summary: Droold plugin version doesn't match the appropriate bundle version
Key: JBTIS-1045
URL: https://issues.jboss.org/browse/JBTIS-1045
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: drools/ jBPM
Affects Versions: 4.4.1.Final
Reporter: Andrej Podhradsky
JBTIS 4.4.1.Final / DevstudioIS 10.1.0.GA contains drools plugins in the following version
{code}
6.5.1.Final-v20161109-054101-B1259
{code}
All related features and plugins also contain the above versions such as
{code}
org.drools.eclipse.feature_6.5.1.Final-v20161109-054101-B1259
org.drools.eclipse_6.5.1.Final-v20161109-054101-B1259.jar
{code}
But if you unzip the drools plugin and look at its bundle version in MANIFEST file you will see
{code}
Bundle-Version: 6.5.0.20161109-054101
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-1045) Drools plugin version doesn't match the appropriate bundle version
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1045?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1045:
-------------------------------------
Summary: Drools plugin version doesn't match the appropriate bundle version (was: Droold plugin version doesn't match the appropriate bundle version)
> Drools plugin version doesn't match the appropriate bundle version
> ------------------------------------------------------------------
>
> Key: JBTIS-1045
> URL: https://issues.jboss.org/browse/JBTIS-1045
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM
> Affects Versions: 4.4.1.Final
> Reporter: Andrej Podhradsky
>
> JBTIS 4.4.1.Final / DevstudioIS 10.1.0.GA contains drools plugins in the following version
> {code}
> 6.5.1.Final-v20161109-054101-B1259
> {code}
> All related features and plugins also contain the above versions such as
> {code}
> org.drools.eclipse.feature_6.5.1.Final-v20161109-054101-B1259
> org.drools.eclipse_6.5.1.Final-v20161109-054101-B1259.jar
> {code}
> But if you unzip the drools plugin and look at its bundle version in MANIFEST file you will see
> {code}
> Bundle-Version: 6.5.0.20161109-054101
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23919) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [server]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23919?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23919.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [server]
> ----------------------------------------------------------------
>
> Key: JBIDE-23919
> URL: https://issues.jboss.org/browse/JBIDE-23919
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [server]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23918) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [openshift]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23918?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23918.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [openshift]
> -------------------------------------------------------------------
>
> Key: JBIDE-23918
> URL: https://issues.jboss.org/browse/JBIDE-23918
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [openshift]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23921) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [webservices]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23921?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23921.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [webservices]
> ---------------------------------------------------------------------
>
> Key: JBIDE-23921
> URL: https://issues.jboss.org/browse/JBIDE-23921
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [webservices]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23920) For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [visual-page-editor-core]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23920?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23920.
------------------------------
Resolution: Done
> For JBIDE 4.4.4.AM1: Prepare for 4.4.4.AM1 / 10.4.0.AM1 [visual-page-editor-core]
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23920
> URL: https://issues.jboss.org/browse/JBIDE-23920
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: visual-page-editor-core
> Reporter: Jeff MAURY
> Assignee: Ilya Buziuk
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.AM1
>
>
> For JBIDE 4.4.4.AM1 [visual-page-editor-core]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.AM1 or 10.4.0.AM1
>
> [Unresolved JIRAs with fixVersion = 4.4.4.AM1, 10.4.0.AM1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.AM1-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.AM1-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.AM1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month