[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-158:
----------------------------------
https://github.com/jbosstools/jbosstools-integration-stack/pull/109 merged
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
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
10 years, 9 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-158:
----------------------------------
Ok - looks good - i installed core first:
https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/
then my local standalone into a clean eclipse and all went well.
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
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
10 years, 9 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-158:
----------------------------------
+1 to JBDS IS requiring JBDS.
Options for an end user are therefore:
1. Install JBDS or JBDS BYOE from Marketplace
2. Launch JBDS or Eclipse
3. Help > Install > Work With > browse for downloaded JBDS IS zip
4. Install
OR
1. Launch Eclipse
2. Help > Install > Work With > browse for downloaded JBDS installer jar or just enter https://devstudio.jboss.com/updates/7.0/
3. Help > Install > Work With > browse to downloaded JBDS IS zip
4. Install
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
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
10 years, 9 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Rob Cernich (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Rob Cernich commented on JBTIS-158:
-----------------------------------
Paul, the standalone zip has a requirement on JBDS, so for a BYOE install, you'll need to add a site for JBDS core (i.e. you need to add the JBDS core and JBDS IS sites). HTH.
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
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
10 years, 9 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-15381:
------------------------------------------
Description:
If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
was:If class is anotated @Vetoed or if its package is annotated @Vetoed, then it
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: CDI
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
--
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
10 years, 9 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-158:
----------------------------------
- I copied the 4.1.3.Final TP repo over to [1] and built the jbdsis-aggregate-disc Jenkins project.
- I expanded the standalone zip and did a p2 install into JBDS 7.
- Install completed successfully (yea)!
- I expanded the standalone zip and did a p2 install into a clean eclipse.
- I got this missing at install time:
Missing requirement: JBoss ESB Project Core Plugin 1.5.300.Final-v20130815-1755-B1189 (org.jboss.tools.esb.project.core 1.5.300.Final-v20130815-1755-B1189) requires 'bundle org.jboss.ide.eclipse.as.classpath.core 0.0.0' but it could not be found
- Is this supposed to install standalone into a clean eclipse?
[1] https://devstudio.jboss.com/updates/7.0.0/7.0.0.Beta1.jbds-is-target-plat...
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
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
10 years, 9 months