Re: GroupId for DayTrader needed.
On 7/24/06, Jason Dillon [EMAIL PROTECTED] wrote: FYI, I have an initial impl of a JDBM-based hybrid repository here: I think it's invaluable to have and it should therefore earn its own task issue in jira, shouldn't it? Unless it's already there, would you add the content to the task? I worry it will lose our attention quickly. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: GroupId for DayTrader needed.
No issue that I know of. Still testing, need to get more details on the unpacked car files, which are causing the longest files... --jason On Jul 23, 2006, at 11:28 PM, Jacek Laskowski wrote: On 7/24/06, Jason Dillon [EMAIL PROTECTED] wrote: FYI, I have an initial impl of a JDBM-based hybrid repository here: I think it's invaluable to have and it should therefore earn its own task issue in jira, shouldn't it? Unless it's already there, would you add the content to the task? I worry it will lose our attention quickly. Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: GroupId for DayTrader needed.
FYI, I have an initial impl of a JDBM-based hybrid repository here:
http://svn.apache.org/repos/asf/geronimo/sandbox/svkmerge/
geronimo-repository/geronimo-repository-providers/geronimo-repository-
jdbm/
This uses files to store the content to be compatible wit the
existing API, and JDBM for the metadata.
Repository fs looks like:
metadata.db
metadata.lg
data / hash (of groupId, artifactId, version) / artifactId-
version.type
If/when when the repo api is abstracted away from files, thrn it
would be easy to put all content into another artifacts.db to reduce
any chance of long filenames (except for the most insane cases).
I added a RepositoryCopier util too, so it would be trivial to make a
command-line version to turn a JDBM-repo into an m2-repo for folks
that don't use windows and prefer to see the files as is.
Have not done it yet, but would be easy to write a tool to add a new
file to and repo. Can either specify the artifact or if built with
maven 2, then the META-INF/maven/* bits can be used to specify the
right groupId/artifactId/version/type to install with. This tool can
also complain if not enough information was given... so it solves the
problem of people copying random artifacts into the repository.
* * *
Also, this http://svn.apache.org/repos/asf/geronimo/sandbox/svkmerge/
geronimo-repository is the new structure I am going to recommend for
future reorg for maven2-based systems, so you might want to take a
peek at the overall tree too. This tree provides encapsulation of
all of the repository components (though currently missing the impls
for m1 and m2 as well as the admin portlets, but will eventually have
them).
NOTE: This is just a POC, no plans yet to move this to trunk in any
way... though eventually I would like to do that.
--jason
On Jul 21, 2006, at 4:34 PM, Dain Sundstrom wrote:
On Jul 20, 2006, at 4:01 PM, Jason Dillon wrote:
It is not just how we use the m2-style repo inside of G, but also
how we build G using m2 that will cause problems for windows peeps.
The later is going to be more trouble to resolve I think.
I'm still thinking it would be a good idea to have some sort of
file-system abstraction for our m2-style repo... in the same way
that SVN has an abstraction... that could use BDB or a regular
file system (ie. FSFS) for actual storage. WIth something like
this, we could have the default distro use a BDB-ish filesystem
and completely resolve the windows file name limitations. With a
set of cli tools we can easily allow the BDB-ish to be converted
to a FSFS.
The repo is an interface. Well it is really three interfaces
depending how much you want to implement:
public interface Repository {
boolean contains(Artifact artifact);
File getLocation(Artifact artifact);
LinkedHashSet getDependencies(Artifact artifact);
}
public interface WriteableRepository extends Repository {
void copyToRepository(File source, Artifact destination,
FileWriteMonitor monitor) throws IOException;
void copyToRepository(InputStream source, int size, Artifact
destination, FileWriteMonitor monitor) throws IOException;
}
public interface ListableRepository extends Repository {
SortedSet list();
SortedSet list(Artifact query);
}
We have an M1 and M2 implementation of these, so if you want
another one you have some good base code to start with.
-dain
Re: GroupId for DayTrader needed.
Anyone know of a Berkeley-DB-ish lib for Java that is compatible with
the ASL? Is the SleepyCat/Berkeley DB Java license compatible? Or
is jdbm any good?
--jason
On Jul 21, 2006, at 4:34 PM, Dain Sundstrom wrote:
On Jul 20, 2006, at 4:01 PM, Jason Dillon wrote:
It is not just how we use the m2-style repo inside of G, but also
how we build G using m2 that will cause problems for windows peeps.
The later is going to be more trouble to resolve I think.
I'm still thinking it would be a good idea to have some sort of
file-system abstraction for our m2-style repo... in the same way
that SVN has an abstraction... that could use BDB or a regular
file system (ie. FSFS) for actual storage. WIth something like
this, we could have the default distro use a BDB-ish filesystem
and completely resolve the windows file name limitations. With a
set of cli tools we can easily allow the BDB-ish to be converted
to a FSFS.
The repo is an interface. Well it is really three interfaces
depending how much you want to implement:
public interface Repository {
boolean contains(Artifact artifact);
File getLocation(Artifact artifact);
LinkedHashSet getDependencies(Artifact artifact);
}
public interface WriteableRepository extends Repository {
void copyToRepository(File source, Artifact destination,
FileWriteMonitor monitor) throws IOException;
void copyToRepository(InputStream source, int size, Artifact
destination, FileWriteMonitor monitor) throws IOException;
}
public interface ListableRepository extends Repository {
SortedSet list();
SortedSet list(Artifact query);
}
We have an M1 and M2 implementation of these, so if you want
another one you have some good base code to start with.
-dain
Re: GroupId for DayTrader needed.
On Jul 21, 2006, at 4:34 PM, Dain Sundstrom wrote:
public interface Repository {
boolean contains(Artifact artifact);
File getLocation(Artifact artifact);
LinkedHashSet getDependencies(Artifact artifact);
}
public interface WriteableRepository extends Repository {
void copyToRepository(File source, Artifact destination,
FileWriteMonitor monitor) throws IOException;
void copyToRepository(InputStream source, int size, Artifact
destination, FileWriteMonitor monitor) throws IOException;
}
These methods that take a File or return a File are not very friendly
for providing a repository implementation that does not actually use
File object directly.
Any reason why these are not URL objects?
--jason
Re: GroupId for DayTrader needed.
On Jul 20, 2006, at 4:01 PM, Jason Dillon wrote:
It is not just how we use the m2-style repo inside of G, but also
how we build G using m2 that will cause problems for windows peeps.
The later is going to be more trouble to resolve I think.
I'm still thinking it would be a good idea to have some sort of
file-system abstraction for our m2-style repo... in the same way
that SVN has an abstraction... that could use BDB or a regular file
system (ie. FSFS) for actual storage. WIth something like this, we
could have the default distro use a BDB-ish filesystem and
completely resolve the windows file name limitations. With a set
of cli tools we can easily allow the BDB-ish to be converted to a
FSFS.
The repo is an interface. Well it is really three interfaces
depending how much you want to implement:
public interface Repository {
boolean contains(Artifact artifact);
File getLocation(Artifact artifact);
LinkedHashSet getDependencies(Artifact artifact);
}
public interface WriteableRepository extends Repository {
void copyToRepository(File source, Artifact destination,
FileWriteMonitor monitor) throws IOException;
void copyToRepository(InputStream source, int size, Artifact
destination, FileWriteMonitor monitor) throws IOException;
}
public interface ListableRepository extends Repository {
SortedSet list();
SortedSet list(Artifact query);
}
We have an M1 and M2 implementation of these, so if you want another
one you have some good base code to start with.
-dain
Re: GroupId for DayTrader needed.
It is not just how we use the m2-style repo inside of G, but also how we build G using m2 that will cause problems for windows peeps. The later is going to be more trouble to resolve I think. I'm still thinking it would be a good idea to have some sort of file- system abstraction for our m2-style repo... in the same way that SVN has an abstraction... that could use BDB or a regular file system (ie. FSFS) for actual storage. WIth something like this, we could have the default distro use a BDB-ish filesystem and completely resolve the windows file name limitations. With a set of cli tools we can easily allow the BDB-ish to be converted to a FSFS. Short of hacking up G to work around the problem... I don't see any other clean way to resolve this problem for our windows users. --jason On Jul 19, 2006, at 7:04 PM, Matt Hogstrom wrote: Hey, I used to have a TRS-80. 32k of RAM...yup, those were the good 'ol days. I agree that shortening the DT artifacts is only moving the bubble around. The fact is that for all of its issues there are a lot more Windows users out there than the *nix OS's. One area to improve things is to eliminate this redundancy: daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT\daytrader-derby- tomcat_streamer.jar-1.2-SNAPSHOT.car At a minimum we burn up 47 characters with daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT where the actual artifact name contains exactly the same information for the most part. I'm not sure what the right solution is here but if we had a creative way to remove the first part we'd get some serious relief. Is the reason we have this so we can use the Maven component directly? If we decided to modify our repository code to do some introspection would that help? Dain, I know you wrote most of the code with David, what are your thoughts on this? Jason Dillon wrote: I think that in general... the m2 repository using the m2 style of artifactId and groupId names is not compatible with Windows. Short of changing the way m2 works or altering the m2 naming standard, I do not see any simple way around this problem. And we are getting hit by this in two places too... building the server, and then again when running the server. I think we need to find a real solution to this issue and not just truncate the names to get around problem... until it pops up again... which is will. And as much as I would love to just give all windows users the shaft and force them to snap out of their microsoft induced blue screen of death, reboot every day, annoying dancing paper clip, stupid file locking, file names can't be longer than 256 insanity... and I would really love to do that... we can't :-( Lucky we don't have to support TRS-80, CPM or Altair users... --jason On Jul 19, 2006, at 7:38 AM, anita kulshreshtha wrote: Jeff, We also need to shorten the artifactId. It makes a good puzzle - Come up with sensible groupId and artifactId such that this does not exceed 256! Example 2 - D:\geronimo-1.2\configs\daytrader-tomcat\target\reposito ry\org\apache\geronimo\configs\daytrader-derby-tomcat_streamer.jar \1.2-SNAPSHOT\daytrader-derby-tomc at_streamer.jar-1.2-SNAPSHOT.car\org.apache.geronimo.modules\ge- activemq-rar\1.2-SNAPSHOT\rar\ activemq-3.2.4-SNAPSHOT.jar This example is taken from http://www.nabble.com/M2-%3A-build-on-Windows-p4914787.html is 256+30 long! Cheers Anita --- Jeff Genender [EMAIL PROTECTED] wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: GroupId for DayTrader needed.
My non-binding, itty-bitty, wimpy, not sure its worth anything vote is for org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 8:15 PM, Prasad Kashyap wrote: OK. I don't have a strong preference to any single groupId name. I believe Matt doesn't either but I'll see if I can get him to clarify that. So between Jeff and Jason, if we can reach a consensus on a name, can we please get the name change done ? Any other proposals ? Any other formalities ? IIf we are planning to drop the m1 build, then I'd like us to start including this in m2 build, with a goal to making the m2 build an exact replica or as close to m1 as possible. Cheers Prasad On 7/18/06, Jason Dillon [EMAIL PROTECTED] wrote: I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
Man, you have some serious windows scars or you need to ease off on the coffee :-) John Jason Dillon wrote: Um... blah... lets go back 10 years and give everything 8.3 names with mad cryptic names in one directory with a slew of meaning-deficient 3 letter suffixes to tell stuff apart. Oh... no... wait, lets create a long file name obfuscation system using ~[0-9] suffixes on truncated filenames... ya that will be better. Or lets just number all files 1-100 Or how about we generate secure randoms for each file name? or... how about lets just put everything into one big sparse file... Or we could have a post processor that takes a normal assembly + config and then truncates everything and adds a metadata descriptor for resolution. No, thats is too much... lets just use one big sparse file... though secure random file names is starting to grow on me. :-P --jason On Jul 18, 2006, at 9:01 PM, John Sisson wrote: I have already run into problems with path lengths in the 1.1 branch with daytrader now we have moved to 1.1.1-SNAPSHOT. See https://issues.apache.org/jira/browse/DAYTRADER-6 Considering the number of developers (and possibly future developers) on the windows platform, we should ensure it works. Even if it means we have to shorten the names. The groupid and artifactIds are just identifiers, you can have nice long descriptions in the pom files if you like :-) John Jason Dillon wrote: I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
Jeff, We also need to shorten the artifactId. It makes a good puzzle - Come up with sensible groupId and artifactId such that this does not exceed 256! Example 2 - D:\geronimo-1.2\configs\daytrader-tomcat\target\reposito ry\org\apache\geronimo\configs\daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT\daytrader-derby-tomc at_streamer.jar-1.2-SNAPSHOT.car\org.apache.geronimo.modules\ge-activemq-rar\1.2-SNAPSHOT\rar\ activemq-3.2.4-SNAPSHOT.jar This example is taken from http://www.nabble.com/M2-%3A-build-on-Windows-p4914787.html is 256+30 long! Cheers Anita --- Jeff Genender [EMAIL PROTECTED] wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: GroupId for DayTrader needed.
I think that in general... the m2 repository using the m2 style of artifactId and groupId names is not compatible with Windows. Short of changing the way m2 works or altering the m2 naming standard, I do not see any simple way around this problem. And we are getting hit by this in two places too... building the server, and then again when running the server. I think we need to find a real solution to this issue and not just truncate the names to get around problem... until it pops up again... which is will. And as much as I would love to just give all windows users the shaft and force them to snap out of their microsoft induced blue screen of death, reboot every day, annoying dancing paper clip, stupid file locking, file names can't be longer than 256 insanity... and I would really love to do that... we can't :-( Lucky we don't have to support TRS-80, CPM or Altair users... --jason On Jul 19, 2006, at 7:38 AM, anita kulshreshtha wrote: Jeff, We also need to shorten the artifactId. It makes a good puzzle - Come up with sensible groupId and artifactId such that this does not exceed 256! Example 2 - D:\geronimo-1.2\configs\daytrader-tomcat\target\reposito ry\org\apache\geronimo\configs\daytrader-derby-tomcat_streamer.jar \1.2-SNAPSHOT\daytrader-derby-tomc at_streamer.jar-1.2-SNAPSHOT.car\org.apache.geronimo.modules\ge- activemq-rar\1.2-SNAPSHOT\rar\ activemq-3.2.4-SNAPSHOT.jar This example is taken from http://www.nabble.com/M2-%3A-build-on-Windows-p4914787.html is 256+30 long! Cheers Anita --- Jeff Genender [EMAIL PROTECTED] wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: GroupId for DayTrader needed.
Hey, I used to have a TRS-80. 32k of RAM...yup, those were the good 'ol days. I agree that shortening the DT artifacts is only moving the bubble around. The fact is that for all of its issues there are a lot more Windows users out there than the *nix OS's. One area to improve things is to eliminate this redundancy: daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT\daytrader-derby-tomcat_streamer.jar-1.2-SNAPSHOT.car At a minimum we burn up 47 characters with daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT where the actual artifact name contains exactly the same information for the most part. I'm not sure what the right solution is here but if we had a creative way to remove the first part we'd get some serious relief. Is the reason we have this so we can use the Maven component directly? If we decided to modify our repository code to do some introspection would that help? Dain, I know you wrote most of the code with David, what are your thoughts on this? Jason Dillon wrote: I think that in general... the m2 repository using the m2 style of artifactId and groupId names is not compatible with Windows. Short of changing the way m2 works or altering the m2 naming standard, I do not see any simple way around this problem. And we are getting hit by this in two places too... building the server, and then again when running the server. I think we need to find a real solution to this issue and not just truncate the names to get around problem... until it pops up again... which is will. And as much as I would love to just give all windows users the shaft and force them to snap out of their microsoft induced blue screen of death, reboot every day, annoying dancing paper clip, stupid file locking, file names can't be longer than 256 insanity... and I would really love to do that... we can't :-( Lucky we don't have to support TRS-80, CPM or Altair users... --jason On Jul 19, 2006, at 7:38 AM, anita kulshreshtha wrote: Jeff, We also need to shorten the artifactId. It makes a good puzzle - Come up with sensible groupId and artifactId such that this does not exceed 256! Example 2 - D:\geronimo-1.2\configs\daytrader-tomcat\target\reposito ry\org\apache\geronimo\configs\daytrader-derby-tomcat_streamer.jar\1.2-SNAPSHOT\daytrader-derby-tomc at_streamer.jar-1.2-SNAPSHOT.car\org.apache.geronimo.modules\ge-activemq-rar\1.2-SNAPSHOT\rar\ activemq-3.2.4-SNAPSHOT.jar This example is taken from http://www.nabble.com/M2-%3A-build-on-Windows-p4914787.html is 256+30 long! Cheers Anita --- Jeff Genender [EMAIL PROTECTED] wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: GroupId for DayTrader needed.
I agree that shortening the DT artifacts is only moving the bubble around. The fact is that for all of its issues there are a lot more Windows users out there than the *nix OS's. Part of me thinks it is my duty to bring down the evil giant maker of crappy software... for the common good of humanity. Windows is a virus and needs to be treated with some serious medicine... or burned to rid the world of its sickness. --jason
Re: GroupId for DayTrader needed.
Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
Note, I'm down for o.a.g.samples for the other bits, but DayTrader has enough modules to warrant its own groupId IMO. --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
OK. I don't have a strong preference to any single groupId name. I believe Matt doesn't either but I'll see if I can get him to clarify that. So between Jeff and Jason, if we can reach a consensus on a name, can we please get the name change done ? Any other proposals ? Any other formalities ? IIf we are planning to drop the m1 build, then I'd like us to start including this in m2 build, with a goal to making the m2 build an exact replica or as close to m1 as possible. Cheers Prasad On 7/18/06, Jason Dillon [EMAIL PROTECTED] wrote: I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
I have already run into problems with path lengths in the 1.1 branch with daytrader now we have moved to 1.1.1-SNAPSHOT. See https://issues.apache.org/jira/browse/DAYTRADER-6 Considering the number of developers (and possibly future developers) on the windows platform, we should ensure it works. Even if it means we have to shorten the names. The groupid and artifactIds are just identifiers, you can have nice long descriptions in the pom files if you like :-) John Jason Dillon wrote: I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
Re: GroupId for DayTrader needed.
Um... blah... lets go back 10 years and give everything 8.3 names with mad cryptic names in one directory with a slew of meaning- deficient 3 letter suffixes to tell stuff apart. Oh... no... wait, lets create a long file name obfuscation system using ~[0-9] suffixes on truncated filenames... ya that will be better. Or lets just number all files 1-100 Or how about we generate secure randoms for each file name? or... how about lets just put everything into one big sparse file... Or we could have a post processor that takes a normal assembly + config and then truncates everything and adds a metadata descriptor for resolution. No, thats is too much... lets just use one big sparse file... though secure random file names is starting to grow on me. :-P --jason On Jul 18, 2006, at 9:01 PM, John Sisson wrote: I have already run into problems with path lengths in the 1.1 branch with daytrader now we have moved to 1.1.1-SNAPSHOT. See https://issues.apache.org/jira/browse/DAYTRADER-6 Considering the number of developers (and possibly future developers) on the windows platform, we should ensure it works. Even if it means we have to shorten the names. The groupid and artifactIds are just identifiers, you can have nice long descriptions in the pom files if you like :-) John Jason Dillon wrote: I think the 'samples' bit is not really necessary here. The groupId is just to organize artifacts in the repo. It does not (and should not) represent the full logical structure or package hierarchy of the application/component. But, I also don't think that it makes sense to artificially shorten either just to hack around platform specific issues either. --jason On Jul 18, 2006, at 12:09 PM, Jeff Genender wrote: I am a big fan of org.apache.geronimo.samples.daytrader. But...are we leading ourselves down the path of a Windows dir size too big nightmare? Jeff Jason Dillon wrote: Why not give it is own: org.apache.geronimo.daytrader --jason On Jul 18, 2006, at 11:59 AM, Prasad Kashyap wrote: The DayTrader project needs a consistent groupId for all it's artifacts. Currently, some of it's artifacts are under the geronimo groupid while others are under the org.apache.geronimo groupid. I discussed this with Matt and we decided to pose this Q to the community. One option is to have a groupId called org.apache.geronimo.samples which will be home to daytrader artifacts, other samples we currently have and ones to come. One other thing to consider is the very long artifactId name of some of daytrader's artifacts. An example is something like daytrader-derby-jetty-streamer. When this is coupled with an equally long groupId name, we'll be close to hitting the path limit on windows. Cheers Prasad
