RE: [JBoss-dev] jboss as full distro in repo
by Alex Pinkin
Tom,
AS 4.0.4 distro is already in the repo (jbossas component). It's
currently used by installer only AFAIK.
If you do a bundled jdpl suite distro including AS, it's probably best
to do this inside JEMS installer.
Hit me up on skype/IM to discuss this. skype: kd5rbu
-Alex
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M
Stark
Sent: Monday, August 28, 2006 8:06 AM
To: JBoss.org development list
Subject: Re: [JBoss-dev] jboss as full distro in repo
Then you need to talk to Alex Pinkin about a jbpm intaller as I'm not
putting the dist in the repo. If you need it today, download it from
sourceforge.
Tom Baeyens wrote:
> i use the jbossas binary components for the compilation dependencies.
>
> but i still need a similar full distro representation as input to
build
> the jpdl suite: packaging that includes jbpm engine and web console
> deployed on jboss + graphical designer
>
> regards, tom.
> tom.baeyens(a)jboss.com
> +32 14 880 900
>
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
20 years
RE: [JBoss-dev] common project structure changes
by Ruel Loehr
1) Ok. We’ll need to setup JIRA accordingly. I’ll figure out how to do this.
Yes, the structure is dorky. I’ll archive the old tags and branches and move each of the independent projects up to the top level.
2) I’ll remove all the jbossbuild related stuff.
3) Defaulting the repo to our own is doable. We’ll talk a little more about this in the meeting on Thursday.
4) That’s an error on my part. I’ll fix the artifact name.
5) The eclipse plugin will generate the classpaths for us. HYPERLINK "http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCommonProject"http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCommonProject – has an example of how to do it
Ruel Loehr
JBoss QA
-----------------------------
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
_____
From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark
Sent: Saturday, August 26, 2006 9:44 AM
To: JBoss.org development list
Subject: Re: [JBoss-dev] common project structure changes
Looking at this in more detail,
1. Based on there trunk directories under each project, we will treat these and distinct projects in terms of releases and have:
HYPERLINK "https://svn.jboss.org/repos/common/common-core/%7btrunk,tags,branches"https://svn.jboss.org/repos/common/common-core/{trunk,tags,branches}
HYPERLINK "https://svn.jboss.org/repos/common/common-logging-jdk/%7btrunk,tags,branches"https://svn.jboss.org/repos/common/common-logging-jdk/{trunk,tags,branches}
HYPERLINK "https://svn.jboss.org/repos/common/common-log4j/%7btrunk,tags,branches"https://svn.jboss.org/repos/common/common-log4j/{trunk,tags,branches}
HYPERLINK "https://svn.jboss.org/repos/common/common-spi/%7btrunk,tags,branches"https://svn.jboss.org/repos/common/common-spi/{trunk,tags,branches}
HYPERLINK "https://svn.jboss.org/repos/common/jbossxb/%7btrunk,tags,branches"https://svn.jboss.org/repos/common/jbossxb/{trunk,tags,branches}
Right now the HYPERLINK "https://svn.jboss.org/repos/common"https://svn.jboss.org/repos/common structure is screwy because its HYPERLINK "https://svn.jboss.org/repos/common/trunk/common-core/trunk"https://svn.jboss.org/repos/common/trunk/common-core/trunk. The top level trunk does not have any meaning with the restucturing because these projects are now independent. HYPERLINK "https://svn.jboss.org/repos/common/%7btags,branches"https://svn.jboss.org/repos/common/{tags,branches} refer to the old monolithic content and has no single trunk analog going forward.
2. The build scripts and tools directory in each project should just be dropped and maven required to be on the users path. Adding the build jars to every single fine grained project is just wasting space in my view. The build scripts and tools are out of date anyway as they are the old jbossbuild versions.
3. Running mvn has it going to ibilio for some jars. I would like that all content comes from the jboss repository, and that we can force this.
[sstark@sstark trunk]$ mvn install
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building JBoss Common Classes
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for up
dates from jbosspluginrepo
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for up
dates from central
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl"http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl
ugins/maven-resources-plugin/2.2/maven-resources-plugin-2.2.pom
1K downloaded
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-p"http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-p
lugins/1/maven-plugins-1.pom
[WARNING] Unable to get resource from repository jbosspluginrepo (HYPERLINK "http://reposit"http://reposit
ory.jboss.com/maven2)
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/plugins/..."http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/plugins/...
3K downloaded
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/maven/maven-parent/1/"http://repository.jboss.com/maven2/org/apache/maven/maven-parent/1/
maven-parent-1.pom
[WARNING] Unable to get resource from repository jbosspluginrepo (HYPERLINK "http://reposit"http://reposit
ory.jboss.com/maven2)
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/ma"http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/ma
ven-parent/1/maven-parent-1.pom
6K downloaded
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/apache/1/apache-1.pom"http://repository.jboss.com/maven2/org/apache/apache/1/apache-1.pom
3K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '403723adb1
ec1a705c65b2780b5803ebffb7819e'; remote = '8902526cc8e0fd0373c42c7f3ddc35560c26b
f59' - RETRYING
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/apache/1/apache-1.pom"http://repository.jboss.com/maven2/org/apache/apache/1/apache-1.pom
3K downloaded
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '403723adb1
ec1a705c65b2780b5803ebffb7819e'; remote = '8902526cc8e0fd0373c42c7f3ddc35560c26b
f59' - IGNORING
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-r"http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-r
esources-plugin/2.2/maven-resources-plugin-2.2.jar
[WARNING] Unable to get resource from repository jbosspluginrepo (HYPERLINK "http://reposit"http://reposit
ory.jboss.com/maven2)
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl"http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl
ugins/maven-resources-plugin/2.2/maven-resources-plugin-2.2.jar
13K downloaded
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for upd
ates from jbosspluginrepo
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for upd
ates from central
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl"http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl
ugins/maven-surefire-plugin/2.2/maven-surefire-plugin-2.2.pom
1K downloaded
Downloading: HYPERLINK "http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-s"http://repository.jboss.com/maven2/org/apache/maven/plugins/maven-s
urefire-plugin/2.2/maven-surefire-plugin-2.2.jar
[WARNING] Unable to get resource from repository jbosspluginrepo (HYPERLINK "http://reposit"http://reposit
ory.jboss.com/maven2)
Downloading: HYPERLINK "http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl"http://ibiblio.lsu.edu/main/pub/packages/maven2/org/apache/maven/pl
ugins/maven-surefire-plugin/2.2/maven-surefire-plugin-2.2.jar
14K downloaded
4. Running mvn starting in the common-core/trunk directory ends up failing because jboss.logging:jboss-logging-spi:jar:1.0.1.TEST can not be found:
[INFO] -------------------------------------------------------------------------
---
[INFO] Failed to resolve artifact.
required artifacts missing:
jboss.logging:jboss-logging-spi:jar:1.0.1.TEST
for the artifact:
jboss.common.core:jboss-common-core:jar:1.0.1.TEST
from the specified remote repositories:
central (HYPERLINK "http://repo1.maven.org/maven2"http://repo1.maven.org/maven2),
jboss (HYPERLINK "http://repository.jboss.com/maven2/"http://repository.jboss.com/maven2/)
Makes sense if these are independent projects. In the past we tried have a parent containing project that tied the source dependencies together so that a build from there built the projects in the correct order. How one defines a build project that combines several source projects together is a doc todo. Ultimately it would be nice to have a maven plugin that created such a build project for an eclipse workspace given the component projects that are in the workspace.
5. Speaking of eclipse, the eclipse projects have broken build paths. It seems what we need to do is define a MAVEN_REPOSITORY variable and update the paths relative to this. However, this introduces the problem of the paths containing the version and thus the classpath becomes dependent on the project pom versions. I suppose there is a maven/eclipse plugin that can keep the project classpath in synch with the pom.xml?
Ruel Loehr wrote:
We’ve been working on the file structure of the jboss common project and are now ready to merge the changes back into the trunk. The changes are substantial, so I want to make sure everyone is clear before I commit them in.
Currently the common project consists of 1 source tree which creates 4 artifacts:
Jboss-archive-browsing.jar
Jboss-common.jar
Jboss-common-client.jar
Namespace.jar
The project has been refactored in a branch (HYPERLINK "https://svn.jboss.org/repos/common/branches/logging_refactoring/"https://svn.jboss.org/repos/common/branches/logging_refactoring/ )
It has been broken into 5 projects
Common-core
Common-logging-jdk
Common-logging-log4j
Common-logging-spi
Jbossxb
Each of these projects builds a single jar. A maven build has been setup for each of these projects. The idea behind these changes is to cleanly separate each project into its own entity.
After these changes are committed, binaries will be published to the repository for all projects and then they will be integrated to jbossAS/trunk.
These changes apply only to the trunk version, not the 4.0 branch.
Thoughts or concerns?
Ruel Loehr
JBoss QA
--
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.10.10/419 - Release Date: 8/15/2006
_____
_______________________________________________
jboss-development mailing list
HYPERLINK "mailto:jboss-development@lists.jboss.org"jboss-development(a)lists.jboss.org
HYPERLINK "https://lists.jboss.org/mailman/listinfo/jboss-development"https://lists.jboss.org/mailman/listinfo/jboss-development
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.6/428 - Release Date: 8/25/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.11.6/428 - Release Date: 8/25/2006
20 years
Thunderbird/Firefox integration issue
by Scott M Stark
Selecting an http link from within thunderbird is not opening it up in
firefox on my new rhel4 box:
Thunderbird version 1.5.0.5 (20060719)
Firefox version Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.5)
Gecko/20060726 Red Hat/1.5.0.5-0.el4.1 Firefox/1.5.0.5
[starksm@succubus ~]$ uname -a
Linux succubus.starkinternational.com 2.6.9-42.0.2.ELsmp #1 SMP Thu Aug
17 17:57:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
Anyone know what setting controls this?
20 years
RE: [JBoss-dev] jboss as full distro in repo
by Tom Baeyens
i use the jbossas binary components for the compilation dependencies.
but i still need a similar full distro representation as input to build
the jpdl suite: packaging that includes jbpm engine and web console
deployed on jboss + graphical designer
regards, tom.
tom.baeyens(a)jboss.com
+32 14 880 900
| -----Original Message-----
| From: jboss-development-bounces(a)lists.jboss.org
| [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
| Of Scott M Stark
| Sent: woensdag 23 augustus 2006 15:34
| To: JBoss.org development list
| Subject: Re: [JBoss-dev] jboss as full distro in repo
|
| I don't see a need for the full distro in the repository. The
| repository is for binary component integration, not releases.
| The jbossas-repo.zip is a canonical representation of the
| dist for input into the jems installer.
|
| Tom Baeyens wrote:
| > i can only find one at
| > http://repository.jboss.com/jbossas/4.0.4.GA/lib/
| > called jbossas-repo.zip
| >
| > the strange thing about this distro is that it doesn't have
| the usual
| > default/all/minimal configuration directories in the server
| directory.
| > instead, the conf and deploy dirs are straight under the server
| > directory. afaict, it is an all configuration that is under the
| > server dir.
| >
| > can i upload normal jboss as distros for versions 4.0.3.SP1 and
| > 4.0.4.GA to the repository ?
| >
| > regards, tom.
| >
| > _______________________________________________
| > jboss-development mailing list
| > jboss-development(a)lists.jboss.org
| > https://lists.jboss.org/mailman/listinfo/jboss-development
| >
|
| _______________________________________________
| jboss-development mailing list
| jboss-development(a)lists.jboss.org
| https://lists.jboss.org/mailman/listinfo/jboss-development
|
20 years
