[JBoss JIRA] (JBIDE-15342) use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15342:
----------------------------------
Summary: use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final
Key: JBIDE-15342
URL: https://issues.jboss.org/browse/JBIDE-15342
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: BPEL
Affects Versions: 4.1.0.Final
Reporter: Nick Boldt
Assignee: Robert (Bob) Brodt
Fix For: 4.1.0.Final
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT.
Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
Once that's fixed and the build is blue, we should release bpel tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15341?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15341:
-------------------------------
Description:
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT.
Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
Once that's fixed and the build is blue, we should release bpel tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.
was:
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT.
Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.
> use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-15341
> URL: https://issues.jboss.org/browse/JBIDE-15341
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: BPEL
> Affects Versions: 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Fix For: 4.1.0.Final
>
>
> Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha1-SNAPSHOT.
> Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
> Once that's fixed and the build is blue, we should release bpel tooling v 1.2.100.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-15341) use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15341:
----------------------------------
Summary: use latest parent pom & target platform so we can release BPEL tooling v 1.2.100.Final
Key: JBIDE-15341
URL: https://issues.jboss.org/browse/JBIDE-15341
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 4.1.0.Final
Reporter: Nick Boldt
Assignee: Koen Aers
Fix For: 4.1.0.Final
Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.Alpha2-SNAPSHOT.
Target platform referenced should be the Kepler version (4.1.x) rather than the Juno version (4.0.0).
Once that's fixed and the build is blue, we should release jbpm3 tooling v 4.5.200.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ]
Denis Golovin edited comment on JBIDE-3628 at 8/14/13 3:31 PM:
---------------------------------------------------------------
Current state. Plugins that are unpacked now:
org.hibernate.eclipse_3.7.0.Alpha1-v20130812-2244
org.hibernate.eclipse.console_3.7.0.Alpha1-v20130812-2244
org.hibernate.eclipse.libs_3.7.0.Alpha1-v20130812-2244
org.jboss.ide.eclipse.archives.core_3.4.100.Alpha1-v20130812-2244
org.jboss.tools.common.gef_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.model_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.model.ui_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.projecttemplates_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.ajax4jsf_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.facelets_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.myfaces_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.richfaces_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.seam_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jst.web.kb_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.vpe_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.docbook_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.html_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.jsp_3.5.0.Alpha1-v20130812-2244
org.mozilla.xpcom_1.9.2.16
org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre
probably all of them cold be jars except xulrunner one, because it contains native libraries
was (Author: dgolovin):
Current state:
org.hibernate.eclipse_3.7.0.Alpha1-v20130812-2244
org.hibernate.eclipse.console_3.7.0.Alpha1-v20130812-2244
org.hibernate.eclipse.libs_3.7.0.Alpha1-v20130812-2244
org.jboss.ide.eclipse.archives.core_3.4.100.Alpha1-v20130812-2244
org.jboss.tools.common.gef_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.model_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.model.ui_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.common.projecttemplates_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.ajax4jsf_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.facelets_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.myfaces_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.richfaces_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jsf.vpe.seam_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.jst.web.kb_3.6.0.Alpha1-v20130812-2244
org.jboss.tools.vpe_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.docbook_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.html_3.5.0.Alpha1-v20130812-2244
org.jboss.tools.vpe.jsp_3.5.0.Alpha1-v20130812-2244
org.mozilla.xpcom_1.9.2.16
org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre
> Plugins should be .jar's not directories for efficiency sake
> ------------------------------------------------------------
>
> Key: JBIDE-3628
> URL: https://issues.jboss.org/browse/JBIDE-3628
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, freemarker, hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: exception.log
>
>
> 65 of our plugins are bundled exploded instead of a .jar
> Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed.
> What should be fixed:
> 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files
> 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files)
> 3. Some plug-ins contain resources registered in XML catalog
> 4. common.projecttemplates contains resources that is used as template for new projects
> 5. Help content that is stored in zip files should be unpacked
> 6. TBD
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months